{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2005-4469 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2005-4469 yet. Limit exposure of the affected software until one is available.","what":"CVE-2005-4469 is a high-severity code injection vulnerability in n/a, published on 22 Dec 2005. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2005-4469 and fix it if it is affected.\n\nWhat it is: CVE-2005-4469 is a high-severity code injection vulnerability in n/a, published on 22 Dec 2005. 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-2005-4469 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-2005-4469/ (Markdown: https://insights.sbomify.com/CVE-2005-4469/index.md)","id":"CVE-2005-4469","markdown":"https://insights.sbomify.com/CVE-2005-4469/index.md","name":"CVE-2005-4469","record":{"aliases":["GHSA-q99f-3fh3-fpw2"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"PHP genealogy software","requires_auth":"none","summary":"Remote attackers can execute arbitrary PHP code via injection in login and registration parameters, requiring immediate upgrade of PHPGedView.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"phpgedview","vendor":"phpgedview"}],"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 direct static code injection vulnerabilities in PHPGedView 3.3.7 and earlier allow remote attackers to execute arbitrary PHP code via (1) the username field in login.php, or the (2) user_language, (3) user_email, and (4) user_gedcomid parameters in login_register.php, which is directly inserted into authenticate.php.","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-2005-4469","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2005"},"n_packages":0,"n_references":11,"next":{"headline":"Integer overflow in n/a","id":"CVE-2005-4470"},"packages":[],"prev":{"headline":"Code injection in n/a","id":"CVE-2005-4468"},"products":["n/a"],"published":"2005-12-22","related":[{"cvss_score":10,"headline":"Multiple unspecified vulnerabilities in PhpGedView before 4.1.5 have unknown impact and attack vectors related to \"a fundamental design flaw","id":"CVE-2008-2064","kev_date_added":null,"published":"2008-05-02"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2004-0030","kev_date_added":null,"published":"2004-01-08"},{"cvss_score":7.5,"headline":"Missing authorization in n/a","id":"CVE-2004-0031","kev_date_added":null,"published":"2004-09-01"},{"cvss_score":7.5,"headline":"Code injection in n/a","id":"CVE-2004-0128","kev_date_added":null,"published":"2004-09-01"},{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2004-0127","kev_date_added":null,"published":"2004-02-04"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2004-0065","kev_date_added":null,"published":"2004-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":"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 via injection in login and registration parameters, requiring immediate upgrade of PHPGedView.","url":"https://insights.sbomify.com/CVE-2005-4469/"}