# CVE-2005-4469: Code injection in n/a

> Remote attackers can execute arbitrary PHP code via injection in login and registration parameters, requiring immediate upgrade of PHPGedView.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Dec 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-q99f-3fh3-fpw2

## What is CVE-2005-4469?

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.

### Official 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.

## Which versions are affected by CVE-2005-4469?

It affects 1 product.


Products: Phpgedview Phpgedview.

## How do I fix CVE-2005-4469?

No fix has been published for CVE-2005-4469 yet. Limit exposure of the affected software until one is available.

## Is CVE-2005-4469 being exploited?

There is no known exploitation of CVE-2005-4469 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2008-2064](https://insights.sbomify.com/CVE-2008-2064/): Multiple unspecified vulnerabilities in PhpGedView before 4.1.5 have unknown impact and attack vectors related to "a fundamental design flaw (critical 10.0)
- [CVE-2004-0030](https://insights.sbomify.com/CVE-2004-0030/): Code injection in n/a (critical 9.8)
- [CVE-2004-0031](https://insights.sbomify.com/CVE-2004-0031/): Missing authorization in n/a (high 7.5)
- [CVE-2004-0128](https://insights.sbomify.com/CVE-2004-0128/): Code injection in n/a (high 7.5)
- [CVE-2004-0127](https://insights.sbomify.com/CVE-2004-0127/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-4469 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2005-4469 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2005-4469/ (Markdown: https://insights.sbomify.com/CVE-2005-4469/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2005-4469
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2005-4469
- OSV: https://osv.dev/vulnerability/CVE-2005-4469

---
From sbomify Insights: https://insights.sbomify.com/CVE-2005-4469/
Summaries are generated and may contain mistakes; the official description above is the record.