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

> Remote attackers can upload arbitrary PHP files via double extensions in PhpWiki, 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:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Apr 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-48h3-fm9c-m4p8

## What is CVE-2007-2025?

CVE-2007-2025 is a high-severity vulnerability in n/a, published on 13 Apr 2007. It can be exploited over the network, with no action from the victim.

### Official description

Unrestricted file upload vulnerability in the UpLoad feature (lib/plugin/UpLoad.php) in PhpWiki 1.3.11p1 allows remote attackers to upload arbitrary PHP files with a double extension, as demonstrated by .php.3, which is interpreted by Apache as being a valid PHP file.

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

It affects 1 product.


Products: Phpwiki Phpwiki.

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

Upgrade to a fixed version.

## Is CVE-2007-2025 being exploited?

There is no known exploitation of CVE-2007-2025 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2007-3193](https://insights.sbomify.com/CVE-2007-3193/): Auth bypass in n/a (critical 10.0)
- [CVE-2007-2024](https://insights.sbomify.com/CVE-2007-2024/): File upload in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-2025 is a high-severity vulnerability in n/a, published on 13 Apr 2007. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-2025 in the wild and no public exploit code.

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

## Sources

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

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