# CVE-2003-0395: Code injection in n/a

> Remote attackers can execute arbitrary PHP code with administrator privileges by injecting code into the User-Agent header, requiring admin interaction.

- **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:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Jun 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-wf6v-m5v4-phr8

## What is CVE-2003-0395?

CVE-2003-0395 is a high-severity code injection vulnerability in n/a, published on 10 Jun 2003. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Ultimate PHP Board (UPB) 1.9 allows remote attackers to execute arbitrary PHP code with UPB administrator privileges via an HTTP request containing the code in the User-Agent header, which is executed when the administrator executes admin_iplog.php.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2003-0395?

It affects 1 product.


Products: Myupb Ultimate Php Board.

## How do I fix CVE-2003-0395?

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

## Is CVE-2003-0395 being exploited?

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

Public exploit code:

- Ultimate PHP Board 1.9 - 'admin_iplog.php' Arbitrary PHP Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2025-61540](https://insights.sbomify.com/CVE-2025-61540/): SQL injection in n/a (medium 6.5)
- [CVE-2025-61539](https://insights.sbomify.com/CVE-2025-61539/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2015-2217](https://insights.sbomify.com/CVE-2015-2217/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-0395 and fix it if it is affected.

What it is: CVE-2003-0395 is a high-severity code injection vulnerability in n/a, published on 10 Jun 2003. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2003-0395 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-2003-0395/ (Markdown: https://insights.sbomify.com/CVE-2003-0395/index.md)
```

## Sources

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

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