CVE-2013-1916 in the critical feed json
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 t…
published 4y ago modified 4mo ago also EUVD-2013-1910
- cvss
- 8.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 12.8%
- EPSS 12.8% chance of exploitation in 30 days, percentile 96%
- public exploits
- 1
- Exploit-DB
Summary
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.
Patch / fix
Is CVE-2013-1916 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- First public exploit (EDB-16181)
- Published
Exploit prediction
12.85% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-16181 WordPress Plugin User Photo Component - Arbitrary File Upload webapps, 2011-02-17
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 8.5 | AV:N/AC:M/Au:S/C:C/I:C/A:C |
Affected products
- n/a WordPress Plugin User Photo
Classification
- Weakness
-
- CWE-434 Unrestricted Upload of File with Dangerous Type
- Technology feeds
References
-
plugins.trac.wordpress.org
/changeset/347137
patch, third-party-advisory
-
exploit-db.com
/exploits/16181
exploit, third-party-advisory, vdb-entry
-
wordpress.org
/plugins/user-photo/#developers
release-notes, third-party-advisory
Sources
- CVE List CVE-2013-1916
- NVD CVE-2013-1916
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.