{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-7099 exists.","fix":"No fix has been published for CVE-2024-7099 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-7099 is a critical SQL injection vulnerability in netease-youdao/qanything, published on 13 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-7099 and fix it if it is affected.\n\nWhat it is: CVE-2024-7099 is a critical SQL injection vulnerability in netease-youdao/qanything, published on 13 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-7099 exists.\n\nAffected product: netease-youdao/qanything. 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-2024-7099/ (Markdown: https://insights.sbomify.com/CVE-2024-7099/index.md)","id":"CVE-2024-7099","markdown":"https://insights.sbomify.com/CVE-2024-7099/index.md","name":"CVE-2024-7099","record":{"aliases":["GHSA-vqmq-g46j-863w"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"QAnything knowledge base","requires_auth":"none","summary":"An attacker can execute arbitrary SQL queries to steal database information from the QAnything knowledge base application.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntr_ai","cpe":[{"product":"qanything","vendor":"qanything"}],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"netease-youdao/qanything version 1.4.1 contains a vulnerability where unsafe data obtained from user input is concatenated in SQL queries, leading to SQL injection. The affected functions include `get_knowledge_base_name`, `from_status_to_status`, `delete_files`, and `get_file_by_status`. An attacker can exploit this vulnerability to execute arbitrary SQL queries, potentially stealing information from the database. The issue is fixed in version 1.4.2.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"SQL Injection in netease-youdao/qanything","id":"CVE-2024-7099","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Bold Page Builder \u003c= 5.0.2 - Authenticated (Contributor+) Stored Cross-Site Scripting via bt_bb_button Shortcode","id":"CVE-2024-7100"},"packages":[],"prev":{"headline":"XML Injection in SFS Consulting's ww.Winsure","id":"CVE-2024-7098"},"products":["netease-youdao/qanything"],"published":"2024-10-13","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2024-25722","kev_date_added":null,"published":"2024-02-11"},{"cvss_score":8.1,"headline":"CSRF due to overly permissive CORS headers in netease-youdao/qanything","id":"CVE-2024-8026","kev_date_added":null,"published":"2025-03-20"}],"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":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-10-15","vendors":["netease-youdao"]},"summary":"An attacker can execute arbitrary SQL queries to steal database information from the QAnything knowledge base application.","url":"https://insights.sbomify.com/CVE-2024-7099/"}