{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-6912 exists.","fix":"No fix has been published for CVE-2006-6912 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-6912 is a high-severity SQL injection vulnerability in Phpmyfaq Phpmyfaq, published on 9 Jan 2007. It can be exploited over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2006-6912 and fix it if it is affected.\n\nWhat it is: CVE-2006-6912 is a high-severity SQL injection vulnerability in Phpmyfaq Phpmyfaq, published on 9 Jan 2007. It can be exploited over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-6912 exists.\n\nAffected product: Phpmyfaq Phpmyfaq. 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-2006-6912/ (Markdown: https://insights.sbomify.com/CVE-2006-6912/index.md)","id":"CVE-2006-6912","markdown":"https://insights.sbomify.com/CVE-2006-6912/index.md","name":"CVE-2006-6912","record":{"aliases":["GHSA-j87h-xx89-rh88"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"phpMyFAQ","requires_auth":"unknown","summary":"Remote attackers can execute arbitrary SQL commands in phpMyFAQ, 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":"phpmyfaq","vendor":"phpmyfaq"}],"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"}],"description":"SQL injection vulnerability in phpMyFAQ 1.6.7 and earlier allows remote attackers to execute arbitrary SQL commands via unspecified vectors, possibly the userfile or filename parameter.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2007-03-01","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2007-03-01","kind":"exploitdb","ref":"3393","stars":null,"title":"phpMyFAQ 1.6.7 - SQL Injection / Command Execution"}],"tier":"weaponised"},"has_fix":null,"headline":"SQL injection in n/a","id":"CVE-2006-6912","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"phpmyfaq:phpmyfaq","products":["phpmyfaq:phpmyfaq"],"type":"sql_injection","year":"2006"},"n_packages":0,"n_references":5,"next":{"headline":"File upload in n/a","id":"CVE-2006-6913"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2006-6911"},"products":["n/a"],"published":"2007-01-09","related":[{"cvss_score":9.8,"headline":"Cross-site Scripting (XSS) - Stored in thorsten/phpmyfaq","id":"CVE-2023-0310","kev_date_added":null,"published":"2023-01-15"},{"cvss_score":9.8,"headline":"Cross-site Scripting (XSS) - Reflected in thorsten/phpmyfaq","id":"CVE-2022-4407","kev_date_added":null,"published":"2022-12-11"},{"cvss_score":9.8,"headline":"Security feature bypass in n/a","id":"CVE-2017-11187","kev_date_added":null,"published":"2017-07-12"},{"cvss_score":9.1,"headline":"phpMyFAQ before 4.1.7 2FA Brute-Force via Session-Scoped Throttle","id":"CVE-2026-76213","kev_date_added":null,"published":"2026-08-19"},{"cvss_score":9.1,"headline":"phpMyFAQ before 4.1.7 WebAuthn Replay Attack via Challenge","id":"CVE-2026-76214","kev_date_added":null,"published":"2026-08-19"},{"cvss_score":9.1,"headline":"Cross-site Scripting (XSS) - DOM in thorsten/phpmyfaq","id":"CVE-2023-5316","kev_date_added":null,"published":"2023-09-30"},{"cvss_score":9.1,"headline":"Cross-site Scripting (XSS) - Stored in thorsten/phpmyfaq","id":"CVE-2023-0306","kev_date_added":null,"published":"2023-01-15"}],"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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"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 phpMyFAQ, potentially compromising database integrity and confidentiality.","url":"https://insights.sbomify.com/CVE-2006-6912/"}