{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-24812 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-24812 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-24812 is a high-severity SQL injection vulnerability in misskey-dev misskey, published on 22 Feb 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-24812 and fix it if it is affected.\n\nWhat it is: CVE-2023-24812 is a high-severity SQL injection vulnerability in misskey-dev misskey, published on 22 Feb 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-24812 in the wild and no public exploit code.\n\nAffected product: misskey-dev misskey. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-24812/ (Markdown: https://insights.sbomify.com/CVE-2023-24812/index.md)","id":"CVE-2023-24812","markdown":"https://insights.sbomify.com/CVE-2023-24812/index.md","name":"CVE-2023-24812","record":{"aliases":["GHSA-cgwp-vmr4-wx4q"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Misskey social platform","requires_auth":"low_privilege","summary":"Attackers can execute SQL commands via the tag search API, potentially reading or modifying database contents.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"misskey","vendor":"misskey"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"Misskey is an open source, decentralized social media platform. In versions prior to 13.3.3 SQL injection is possible due to insufficient parameter validation in the note search API by tag (notes/search-by-tag). This has been fixed in version 13.3.3. Users are advised to upgrade. Users unable to upgrade should block access to the `api/notes/search-by-tag` endpoint.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"SQL injection of notes/search-by-tag","id":"CVE-2023-24812","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"URI validation failure on SVG parsing. Bypass of CVE-2023-23924","id":"CVE-2023-24813"},"packages":[],"prev":{"headline":"Cross site scripting (XSS) vulnerability using url preview in Misskey","id":"CVE-2023-24811"},"products":["misskey"],"published":"2023-02-22","related":[{"cvss_score":9.3,"headline":"Misskey's Incomplete Patch of CVE-2024-52591 Leads to Forgery of Federated Notes","id":"CVE-2025-25306","kev_date_added":null,"published":"2025-03-10"},{"cvss_score":9.3,"headline":"Misskey's missing signature validation allows arbitrary users to impersonate any remote user.","id":"CVE-2023-49079","kev_date_added":null,"published":"2023-11-29"},{"cvss_score":9.2,"headline":"Misskey lacks proper authorization checks and input validation","id":"CVE-2026-28431","kev_date_added":null,"published":"2026-03-09"},{"cvss_score":9.1,"headline":"Misskey vulnerable to improper authorization when accessing with third-party application","id":"CVE-2023-52139","kev_date_added":null,"published":"2023-12-29"},{"cvss_score":8.8,"headline":"Missing validation allows spoofed profiles in Misskey","id":"CVE-2024-52590","kev_date_added":null,"published":"2024-12-18"},{"cvss_score":8.8,"headline":"Missing validation allows spoofed profiles and notes in Misskey","id":"CVE-2024-52591","kev_date_added":null,"published":"2024-12-18"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-03-10","vendors":["misskey-dev"]},"summary":"Attackers can execute SQL commands via the tag search API, potentially reading or modifying database contents.","url":"https://insights.sbomify.com/CVE-2023-24812/"}