# CVE-2013-1916: File upload in WordPress Plugin User Photo

> An attacker can upload a malicious backdoor via the User Photo plugin, leading to remote code execution on the WordPress server.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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 Jun 2022
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-mfp3-hghm-2qc5

## What is CVE-2013-1916?

CVE-2013-1916 is a high-severity vulnerability in WordPress Plugin User Photo, published on 24 Jun 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In WordPress Plugin User Photo 0.9.4, when a photo is uploaded, it is only partially validated and it is possible to upload a backdoor on the server hosting WordPress. This backdoor can be called (executed) even if the photo has not been yet approved.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2013-1916?

It affects 1 product.


Products: User Photo Project User Photo.

## How do I fix CVE-2013-1916?

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

## Is CVE-2013-1916 being exploited?

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

Public exploit code:

- WordPress Plugin User Photo Component - Arbitrary File Upload (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-1916 and fix it if it is affected.

What it is: CVE-2013-1916 is a high-severity vulnerability in WordPress Plugin User Photo, published on 24 Jun 2022. 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-2013-1916 exists.

Affected product: WordPress Plugin User Photo. 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-2013-1916/ (Markdown: https://insights.sbomify.com/CVE-2013-1916/index.md)
```

## Sources

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

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