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

> Remote attackers can upload and execute arbitrary PHP files via null byte injection in the filename parameter of the forum write script.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Apr 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-r6w7-xqr4-v3v2

## What is CVE-2007-2182?

CVE-2007-2182 is a medium-severity vulnerability in n/a, published on 24 Apr 2007. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Unrestricted file upload vulnerability in forum_write.php in Maran PHP Forum allows remote attackers to upload and execute arbitrary PHP files via a trailing %00 in a filename in the page parameter.

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

It affects 1 product.


Products: Maran Php Forum.

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

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

## Is CVE-2007-2182 being exploited?

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

Public exploit code:

- Maran PHP Forum - 'forum_write.php' Remote Code Execution (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-2182 is a medium-severity vulnerability in n/a, published on 24 Apr 2007. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-2182 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-2182/ (Markdown: https://insights.sbomify.com/CVE-2007-2182/index.md)
```

## Sources

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

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