{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2007-6299 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2007-6299 yet. Limit exposure of the affected software until one is available.","what":"CVE-2007-6299 is a high-severity SQL injection vulnerability in Drupal Drupal, published on 10 Dec 2007. It can be exploited over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2007-6299 and fix it if it is affected.\n\nWhat it is: CVE-2007-6299 is a high-severity SQL injection vulnerability in Drupal Drupal, published on 10 Dec 2007. It can be exploited over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2007-6299 in the wild and no public exploit code.\n\nAffected product: Drupal Drupal. 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-2007-6299/ (Markdown: https://insights.sbomify.com/CVE-2007-6299/index.md)","id":"CVE-2007-6299","markdown":"https://insights.sbomify.com/CVE-2007-6299/index.md","name":"CVE-2007-6299","record":{"aliases":["GHSA-vqfh-h9j7-97mw"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Drupal CMS","requires_auth":"unknown","summary":"Remote attackers can execute arbitrary SQL commands in Drupal via vulnerable contributed modules, potentially compromising database integrity and confidentiality.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"drupal","vendor":"drupal"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"},{"id":"CWE-20","name":"Improper Input Validation"}],"description":"Multiple SQL injection vulnerabilities in Drupal and vbDrupal 4.7.x before 4.7.9 and 5.x before 5.4 allow remote attackers to execute arbitrary SQL commands via modules that pass input to the taxonomy_select_nodes function, as demonstrated by the (1) taxonomy_menu, (2) ajaxLoader, and (3) ubrowser contributed modules.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"SQL injection in n/a","id":"CVE-2007-6299","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"drupal:drupal","products":["drupal:drupal"],"type":"sql_injection","year":"2007"},"n_packages":0,"n_references":11,"next":{"headline":"Cross-site request forgery in n/a","id":"CVE-2007-6300"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2007-6298"},"products":["n/a"],"published":"2007-12-10","related":[{"cvss_score":9.8,"headline":"Drupal Core SQL Injection","id":"CVE-2026-9082","kev_date_added":"2026-05-22","published":"2026-05-20"},{"cvss_score":8.8,"headline":"Drupal core Un-restricted Upload of File","id":"CVE-2020-13671","kev_date_added":"2022-01-18","published":"2020-11-20"},{"cvss_score":8.1,"headline":"Drupal Core Remote Code Execution","id":"CVE-2019-6340","kev_date_added":"2022-03-25","published":"2019-02-21"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2009-3352","kev_date_added":null,"published":"2009-09-24"},{"cvss_score":9.8,"headline":"Drupal core - Less critical - Gadget chain - SA-CORE-2024-006","id":"CVE-2024-55636","kev_date_added":null,"published":"2024-12-09"},{"cvss_score":9.8,"headline":"Drupal core - Moderately critical - Gadget chain - SA-CORE-2024-007","id":"CVE-2024-55637","kev_date_added":null,"published":"2024-12-09"},{"cvss_score":9.8,"headline":"Drupal core - Moderately critical - Gadget chain - SA-CORE-2024-008","id":"CVE-2024-55638","kev_date_added":null,"published":"2024-12-09"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary SQL commands in Drupal via vulnerable contributed modules, potentially compromising database integrity and confidentiality.","url":"https://insights.sbomify.com/CVE-2007-6299/"}