# CVE-2008-5695: File upload in n/a

> Authenticated users with upload and options capabilities can execute arbitrary code by uploading a PHP script and activating it as a plugin.

- **Severity:** High 8.5 (`AV:N/AC:M/Au:S/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Dec 2008
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2008-5695, GHSA-qjrf-4pw9-57w4

## What is CVE-2008-5695?

CVE-2008-5695 is a high-severity vulnerability in Wordpress Wordpress, published on 19 Dec 2008. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

wp-admin/options.php in WordPress MU before 1.3.2, and WordPress 2.3.2 and earlier, does not properly validate requests to update an option, which allows remote authenticated users with manage_options and upload_files capabilities to execute arbitrary code by uploading a PHP script and adding this script's pathname to active_plugins.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2008-5695?

It affects 2 products.


Products: Wordpress Wordpress, Wordpress Wordpress Mu.

## How do I fix CVE-2008-5695?

Upgrade to a fixed version.

## Is CVE-2008-5695 being exploited?

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

Public exploit code:

- WordPress MU < 1.3.2 - 'active_plugins' Code Execution (exploitdb)

## Other vulnerabilities in Wordpress Wordpress

- [CVE-2026-63030](https://insights.sbomify.com/CVE-2026-63030/): WordPress Core Interpretation Conflict (critical 9.8, exploited in the wild)
- [CVE-2026-87902](https://insights.sbomify.com/CVE-2026-87902/): WordPress Core Remote File Inclusion (high 8.1, exploited in the wild)
- [CVE-2026-60137](https://insights.sbomify.com/CVE-2026-60137/): WordPress Core SQL Injection (medium 5.9, exploited in the wild)
- [CVE-2012-2399](https://insights.sbomify.com/CVE-2012-2399/): Cross-site scripting in n/a (critical 10.0)
- [CVE-2012-2400](https://insights.sbomify.com/CVE-2012-2400/): Other in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-5695 and fix it if it is affected.

What it is: CVE-2008-5695 is a high-severity vulnerability in Wordpress Wordpress, published on 19 Dec 2008. 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-2008-5695 exists.

Affected product: Wordpress Wordpress. 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-2008-5695/ (Markdown: https://insights.sbomify.com/CVE-2008-5695/index.md)
```

## Sources

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

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