# CVE-2004-0030: Code injection in n/a

> Remote attackers can execute arbitrary PHP code in PHPGEDVIEW by manipulating the PGV_BASE_DIRECTORY parameter to include a remote file.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jan 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-xc2p-7wgh-ffh3

## What is CVE-2004-0030?

CVE-2004-0030 is a critical code injection vulnerability in n/a, published on 8 Jan 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PHP remote file inclusion vulnerability in (1) functions.php, (2) authentication_index.php, and (3) config_gedcom.php for PHPGEDVIEW 2.61 allows remote attackers to execute arbitrary PHP code by modifying the PGV_BASE_DIRECTORY parameter to reference a URL on a remote web server that contains the code.

Weakness: CWE-829 (Inclusion of Functionality from Untrusted Control Sphere)

## Which versions are affected by CVE-2004-0030?

It affects 1 product.


Products: Phpgedview Phpgedview.

## How do I fix CVE-2004-0030?

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

## Is CVE-2004-0030 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-0030 exists.

Public exploit code:

- PHPGedView 2.61 - Multiple Remote File Inclusions (exploitdb)

## 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-2005-4469](https://insights.sbomify.com/CVE-2005-4469/): Code injection in n/a (high 7.5)
- [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-2004-0030 and fix it if it is affected.

What it is: CVE-2004-0030 is a critical code injection vulnerability in n/a, published on 8 Jan 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-0030 exists.

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-2004-0030/ (Markdown: https://insights.sbomify.com/CVE-2004-0030/index.md)
```

## Sources

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

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