{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-4437 exists.","fix":"No fix has been published for CVE-2006-4437 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-4437 is a high-severity code injection vulnerability in n/a, published on 14 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-4437 and fix it if it is affected.\n\nWhat it is: CVE-2006-4437 is a high-severity code injection vulnerability in n/a, published on 14 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-4437 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-4437/ (Markdown: https://insights.sbomify.com/CVE-2006-4437/index.md)","id":"CVE-2006-4437","markdown":"https://insights.sbomify.com/CVE-2006-4437/index.md","name":"CVE-2006-4437","record":{"aliases":["GHSA-7vfj-ch9m-m42j"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Tagger LE","requires_auth":"none","summary":"Remote attackers can execute arbitrary PHP code in Tagger LE via eval injection in multiple scripts without authentication.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"flexera","cpe":[{"product":"tagger_le","vendor":"venture_nine"}],"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":"Eval injection vulnerability in Tagger LE allows remote attackers to execute arbitrary PHP code via the query string in (1) tags.php, (2) sign.php, and (3) admin/index.php.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2006-08-09","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2006-08-09","kind":"exploitdb","ref":"2157","stars":null,"title":"Tagger Luxury Edition - 'BBCodeFile' Remote File Inclusion"}],"tier":"weaponised"},"has_fix":null,"headline":"Code injection in n/a","id":"CVE-2006-4437","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2006"},"n_packages":0,"n_references":10,"next":{"headline":"Memory corruption in n/a","id":"CVE-2006-4438"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2006-4436"},"products":["n/a"],"published":"2006-09-14","related":[],"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 execute arbitrary PHP code in Tagger LE via eval injection in multiple scripts without authentication.","url":"https://insights.sbomify.com/CVE-2006-4437/"}