{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2006-4429 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2006-4429 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-4429 is a high-severity code injection vulnerability in n/a, published on 29 Aug 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-4429 and fix it if it is affected.\n\nWhat it is: CVE-2006-4429 is a high-severity code injection vulnerability in n/a, published on 29 Aug 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-4429 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-4429/ (Markdown: https://insights.sbomify.com/CVE-2006-4429/index.md)","id":"CVE-2006-4429","markdown":"https://insights.sbomify.com/CVE-2006-4429/index.md","name":"CVE-2006-4429","record":{"aliases":["GHSA-mjcp-8594-qxpc"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"PHlyMail Lite","requires_auth":"none","summary":"Remote attackers can execute arbitrary PHP code in PHlyMail Lite via a URL parameter in the email handler, despite disputes regarding direct access prevention.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"phlymail_lite","vendor":"phlymail"}],"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":"PHP remote file inclusion vulnerability in handlers/email/mod.output.php in PHlyMail Lite 3.4.4 and earlier (Build 3.04.04) allows remote attackers to execute arbitrary PHP code via a URL in the _PM_[path][handler] parameter, a different vector than CVE-2006-4291.  NOTE: This issue has been disputed by a third party, who states that the _IN_PHM_ declaration prevents this file from being called directly","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":"Code injection in n/a","id":"CVE-2006-4429","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2006"},"n_packages":0,"n_references":3,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2006-4430"},"packages":[],"prev":{"headline":"Code injection in n/a","id":"CVE-2006-4428"},"products":["n/a"],"published":"2006-08-29","related":[{"cvss_score":5.1,"headline":"File upload in n/a","id":"CVE-2006-4291","kev_date_added":null,"published":"2006-08-22"}],"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 PHP code in PHlyMail Lite via a URL parameter in the email handler, despite disputes regarding direct access prevention.","url":"https://insights.sbomify.com/CVE-2006-4429/"}