CVE-2013-2010 in the critical feed json
WordPress W3 Total Cache Plugin 0.9.2.8 has a Remote PHP Code Execution Vulnerability
published 2020-02-12 6 y ago modified 2026-06-16 4 mo ago also EUVD-2013-2001
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 73.9%
- EPSS 73.9% chance of exploitation in 30 days, percentile 99.4%
- public exploits
- 2
- Metasploit, Exploit-DB
Summary
WordPress W3 Total Cache Plugin 0.9.2.8 has a Remote PHP Code Execution Vulnerability
Timeline
- First public exploit (Metasploit exploit/unix/webapp/wp_total_cache_exec)
- Published
Exploit prediction
73.86% chance of exploitation in the next 30 days, higher than 99.4% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Metasploit exploit/unix/webapp/wp_total_cache_exec WordPress W3 Total Cache PHP Code Execution metasploit exploit, excellent rank, 2013-04-17
- EDB-25137 WordPress Plugin W3 Total Cache - PHP Code Execution (Metasploit) remote, 2013-05-01
- packetstormsecurity.com http://packetstormsecurity.com/files/130999/WordPress-W3-Total-Cache-PHP-Code-Execution.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Affected products
- W3 Total Cache Plugin authors W3 Total Cache Plugin
Classification
- Weakness
-
- CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component
- Technology feeds
References
-
packetstormsecurity.com
/files/130999/WordPress-W3-Total-Cache-PHP-Code-Execution.html
exploit, third-party-advisory, vdb-entry
-
exploit-db.com
/exploits/25137
exploit, third-party-advisory, vdb-entry
-
securityfocus.com
/bid/59316
third-party-advisory, vdb-entry
-
openwall.com
/lists/oss-security/2013/04/24/9
mailing-list, third-party-advisory
Sources
- CVE List CVE-2013-2010
- NVD CVE-2013-2010
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.