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

> Remote attackers can execute arbitrary PHP code via remote file inclusion in EasyDynamicPages by manipulating the edp_relative_path parameter.

- **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:** 15 Jan 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-78qh-r4jf-4h7r

## What is CVE-2004-0073?

CVE-2004-0073 is a high-severity code injection vulnerability in n/a, published on 15 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) config.php and (2) config_page.php for EasyDynamicPages 2.0 allows remote attackers to execute arbitrary PHP code by modifying the edp_relative_path parameter to reference a URL on a remote web server that contains a malicious serverdata.php script.

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

It affects 1 product.


Products: Stoitsov Easydynamicpages.

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

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

## Is CVE-2004-0073 being exploited?

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

Public exploit code:

- EasyDynamicPages 1.0 - 'config_page.php' PHP Remote File Inclusion (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-0073 and fix it if it is affected.

What it is: CVE-2004-0073 is a high-severity code injection vulnerability in n/a, published on 15 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-0073 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-0073/ (Markdown: https://insights.sbomify.com/CVE-2004-0073/index.md)
```

## Sources

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

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