{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-4592 exists.","fix":"No fix has been published for CVE-2006-4592 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-4592 is a high-severity SQL injection vulnerability in n/a, published on 6 Sep 2006. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2006-4592 and fix it if it is affected.\n\nWhat it is: CVE-2006-4592 is a high-severity SQL injection vulnerability in n/a, published on 6 Sep 2006. 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-2006-4592 exists.\n\nAffected product: n/a. 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-4592/ (Markdown: https://insights.sbomify.com/CVE-2006-4592/index.md)","id":"CVE-2006-4592","markdown":"https://insights.sbomify.com/CVE-2006-4592/index.md","name":"CVE-2006-4592","record":{"aliases":["GHSA-wr42-4v57-8jp9"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Simple Blog","requires_auth":"none","summary":"Remote attackers can perform SQL injection via the id parameter in Simple Blog due to incomplete blacklist filtering, potentially accessing or modifying database content.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"simple_blog","vendor":"8pixel.net"}],"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":[],"description":"Incomplete blacklist vulnerability in default.asp in 8pixel.net Simple Blog 2.3 and earlier allows remote attackers to conduct SQL injection attacks via \"\u003e\" characters in the id parameter, which are not filtered by the protection mechanism.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2006-09-04","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2006-09-04","kind":"exploitdb","ref":"2296","stars":null,"title":"SimpleBlog 2.3 - 'id' SQL Injection"}],"tier":"weaponised"},"has_fix":null,"headline":"SQL injection in n/a","id":"CVE-2006-4592","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2006"},"n_packages":0,"n_references":6,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2006-4593"},"packages":[],"prev":{"headline":"Code injection in n/a","id":"CVE-2006-4591"},"products":["n/a"],"published":"2006-09-06","related":[{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2007-4055","kev_date_added":null,"published":"2007-07-30"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2006-6191","kev_date_added":null,"published":"2006-12-01"},{"cvss_score":7.5,"headline":"Missing authorization in n/a","id":"CVE-2006-6192","kev_date_added":null,"published":"2006-12-01"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2006-4300","kev_date_added":null,"published":"2006-08-23"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2006-0240","kev_date_added":null,"published":"2006-01-18"},{"cvss_score":5.8,"headline":"Cross-site scripting in n/a","id":"CVE-2006-0239","kev_date_added":null,"published":"2006-01-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":"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 perform SQL injection via the id parameter in Simple Blog due to incomplete blacklist filtering, potentially accessing or modifying database content.","url":"https://insights.sbomify.com/CVE-2006-4592/"}