{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2006-1104 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2006-1104 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-1104 is a high-severity SQL injection vulnerability in n/a, published on 9 Mar 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-1104 and fix it if it is affected.\n\nWhat it is: CVE-2006-1104 is a high-severity SQL injection vulnerability in n/a, published on 9 Mar 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2006-1104 in the wild and no public exploit code.\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-1104/ (Markdown: https://insights.sbomify.com/CVE-2006-1104/index.md)","id":"CVE-2006-1104","markdown":"https://insights.sbomify.com/CVE-2006-1104/index.md","name":"CVE-2006-1104","record":{"aliases":["GHSA-r397-cwxg-8f8r"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Pixelpost blog software","requires_auth":"none","summary":"Remote attackers can execute arbitrary SQL commands via vulnerable parameters and headers in Pixelpost, potentially compromising database integrity.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"pixelpost","vendor":"pixelpost"}],"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":"Multiple SQL injection vulnerabilities in Pixelpost 1.5 beta 1 and earlier allow remote attackers to execute arbitrary SQL commands via (1) the showimage parameter in index.php; and the (2) USER_AGENT, (3) HTTP_REFERER, and (4) HTTP_HOST HTTP header fields as used in the book_vistor function in includes/functions.php.  NOTE: the vendor has disputed some issues from the original disclosure, but due to the vagueness of the dispute, it is not clear whether the vendor is disputing this particular issue.","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-2006-1104","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2006"},"n_packages":0,"n_references":7,"next":{"headline":"Information disclosure in n/a","id":"CVE-2006-1105"},"packages":[],"prev":{"headline":"Null dereference in n/a","id":"CVE-2006-1103"},"products":["n/a"],"published":"2006-03-09","related":[{"cvss_score":9.8,"headline":"pixelpost 1.7.1 has SQL injection","id":"CVE-2009-4899","kev_date_added":null,"published":"2019-10-28"},{"cvss_score":8.8,"headline":"Cross-site request forgery in pixelpost","id":"CVE-2010-3305","kev_date_added":null,"published":"2019-11-12"},{"cvss_score":7.2,"headline":"Code injection in Pixelpost","id":"CVE-2018-0604","kev_date_added":null,"published":"2018-06-26"},{"cvss_score":7.2,"headline":"SQL injection in Pixelpost","id":"CVE-2018-0606","kev_date_added":null,"published":"2018-06-26"},{"cvss_score":6.8,"headline":"Path traversal in n/a","id":"CVE-2008-3365","kev_date_added":null,"published":"2008-07-30"},{"cvss_score":6.8,"headline":"SQL injection in n/a","id":"CVE-2008-0358","kev_date_added":null,"published":"2008-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)"}],"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 via vulnerable parameters and headers in Pixelpost, potentially compromising database integrity.","url":"https://insights.sbomify.com/CVE-2006-1104/"}