# CVE-2007-0370: File upload in n/a

> Remote administrators can upload arbitrary PHP code via unrestricted file upload in phpBP, leading to remote code execution.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jan 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-v9qg-p6jf-339r

## What is CVE-2007-0370?

CVE-2007-0370 is a high-severity vulnerability in n/a, published on 19 Jan 2007. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Unrestricted file upload vulnerability in index.php in phpBP RC3 (2.204) and earlier allows remote administrators to inject arbitrary PHP code into an upload/banners/ file via a banners add operation that uploads the PHP code through an image_form parameter specifying a multiple-extension filename such as .jpg.vil.gif.php, which is stored in upload/banners/ under a different name, and executable via a direct request.  NOTE: a separate SQL injection issue could be leveraged to make this vulnerability reachable by remote unauthenticated attackers.

## Which versions are affected by CVE-2007-0370?

It affects 1 product.


Products: Phpbp Phpbp.

## How do I fix CVE-2007-0370?

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

## Is CVE-2007-0370 being exploited?

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

Public exploit code:

- phpBP RC3 (2.204) - SQL Injection / Remote Code Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-1408](https://insights.sbomify.com/CVE-2008-1408/): SQL injection in n/a (high 7.5)
- [CVE-2007-0369](https://insights.sbomify.com/CVE-2007-0369/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-0370 and fix it if it is affected.

What it is: CVE-2007-0370 is a high-severity vulnerability in n/a, published on 19 Jan 2007. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-0370 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-2007-0370/ (Markdown: https://insights.sbomify.com/CVE-2007-0370/index.md)
```

## Sources

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

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