CVE-2013-2010

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 74% (99th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Weaponized
9.8EG
EchelonGraph verdictMitigate this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 74%
  • Public exploit code is available (Metasploit, Exploit-DB (verified), epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 74%CVSS: 9.8Exploit: Metasploit · Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

WordPress W3 Total Cache Plugin 0.9.2.8 has a Remote PHP Code Execution Vulnerability

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
78
EG Risk 78/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation74% × 40%
Automatability30% × 15%
CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
74%
EPSS %ILE
99th
KEV
Not listed

CISA SSVCTrack at low, Track* at medium and Attend at high mission impact.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation public PoC (EG-KEV: weaponized) · Automatable unknown (not published for this CVE) · Technical impact total (CVSS ≥ 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

February 12, 2020

Last Modified

November 21, 2024

Advisory Details (4)

Auto-updated Oct 7, 2026
🔬 Proof of concept available. No fix on record yet.
generic

CVE-2013-2010 - PSIRT.COM

http://www.securityfocus.com/bid/59316
generic

oss-security - W3 Total Cache 0.9.2.8 Remote Code Exec

http://www.openwall.com/lists/oss-security/2013/04/24/9
generic🟡 PoC Available

WordPress Plugin W3 Total Cache - PHP Code Execution (Metasploit) - PHP remote Exploit

http://www.exploit-db.com/exploits/25137
generic

Packet Storm

http://packetstormsecurity.com/files/130999/WordPress-W3-Total-Cache-PHP-Code-Execution.html

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 3× in last 7d / 10× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-10 19:54 UTCEPSS rescore
  2. 2026-10-07 23:39 UTCEPSS rescore
  3. 2026-10-06 15:10 UTCEPSS rescore
  4. 2026-09-29 20:14 UTCEG score recompute
  5. 2026-09-26 15:52 UTCEPSS rescore
  6. 2026-09-24 13:57 UTCEPSS rescore
  7. 2026-09-18 19:21 UTCEPSS rescore
  8. 2026-09-15 03:04 UTCEPSS rescore
  9. 2026-09-13 16:40 UTCEPSS rescore
  10. 2026-09-12 14:55 UTCEPSS rescore
  11. 2026-09-06 13:42 UTCEPSS rescore
  12. 2026-09-05 15:22 UTCEPSS rescore
  13. 2026-09-04 13:55 UTCEPSS rescore
  14. 2026-09-02 14:06 UTCEPSS rescore
  15. 2026-09-01 13:47 UTCEPSS rescore
  16. 2026-08-26 14:40 UTCEPSS rescore
  17. 2026-08-24 07:23 UTCEPSS rescore
  18. 2026-08-21 23:44 UTCEPSS rescore
  19. 2026-08-19 16:59 UTCEPSS rescore
  20. 2026-08-16 02:09 UTCEPSS rescore
  21. 2026-08-12 13:45 UTCEPSS rescore
  22. 2026-08-07 16:21 UTCEPSS rescore
  23. 2026-08-05 19:12 UTCEPSS rescore
  24. 2026-07-30 01:26 UTCEPSS rescore
  25. 2026-07-28 15:31 UTCEPSS rescore
Show 57 more
  1. 2026-07-25 14:12 UTCEPSS rescore
  2. 2026-07-23 01:09 UTCEG score recompute
  3. 2026-07-23 00:13 UTCEG score recompute
  4. 2026-07-22 21:51 UTCEG score recompute
  5. 2026-07-22 14:04 UTCEPSS rescore
  6. 2026-07-22 14:04 UTCEPSS rescore
  7. 2026-07-21 15:21 UTCEPSS rescore
  8. 2026-07-19 14:27 UTCEPSS rescore
  9. 2026-07-19 14:27 UTCEPSS rescore
  10. 2026-07-18 10:00 UTCEPSS rescore
  11. 2026-07-16 16:58 UTCEPSS rescore
  12. 2026-07-15 16:54 UTCEPSS rescore
  13. 2026-07-15 16:54 UTCEPSS rescore
  14. 2026-07-13 22:26 UTCEPSS rescore
  15. 2026-07-13 06:08 UTCEPSS rescore
  16. 2026-07-11 08:23 UTCEPSS rescore
  17. 2026-07-05 02:26 UTCEPSS rescore
  18. 2026-07-01 15:02 UTCEPSS rescore
  19. 2026-06-30 23:19 UTCEPSS rescore
  20. 2026-06-30 23:19 UTCEPSS rescore
  21. 2026-06-28 14:03 UTCEPSS rescore
  22. 2026-06-28 04:53 UTCEPSS rescore
  23. 2026-06-28 04:53 UTCEPSS rescore
  24. 2026-06-25 13:46 UTCEPSS rescore
  25. 2026-06-24 14:02 UTCEPSS rescore
  26. 2026-06-24 14:02 UTCEPSS rescore
  27. 2026-06-23 21:30 UTCEPSS rescore
  28. 2026-06-21 14:53 UTCEPSS rescore
  29. 2026-06-21 01:57 UTCEPSS rescore
  30. 2026-06-21 01:56 UTCEPSS rescore
  31. 2026-06-18 17:49 UTCEPSS rescore
  32. 2026-06-18 17:49 UTCEPSS rescore
  33. 2026-06-16 17:49 UTCEPSS rescore
  34. 2026-06-16 17:49 UTCEPSS rescore
  35. 2026-06-15 17:44 UTCEPSS rescore
  36. 2026-06-12 23:08 UTCEPSS rescore
  37. 2026-06-11 13:56 UTCEPSS rescore
  38. 2026-06-07 15:22 UTCEPSS rescore
  39. 2026-06-06 13:45 UTCEPSS rescore
  40. 2026-06-06 13:45 UTCEPSS rescore
  41. 2026-06-05 22:44 UTCEPSS rescore
  42. 2026-06-05 22:44 UTCEPSS rescore
  43. 2026-06-05 06:08 UTCEPSS rescore
  44. 2026-06-05 06:08 UTCEPSS rescore
  45. 2026-06-02 20:10 UTCEPSS rescore
  46. 2026-06-02 20:10 UTCEPSS rescore
  47. 2026-06-01 13:49 UTCEPSS rescore
  48. 2026-06-01 13:49 UTCEPSS rescore
  49. 2026-05-31 00:14 UTCEPSS rescore
  50. 2026-05-31 00:14 UTCEPSS rescore
  51. 2026-05-27 13:38 UTCEPSS rescore
  52. 2026-05-27 13:38 UTCEPSS rescore
  53. 2026-05-27 07:51 UTCEG score recompute
  54. 2026-05-27 07:51 UTCGHSA enrichment
  55. 2026-05-26 07:16 UTCEPSS rescore
  56. 2026-05-26 07:16 UTCEPSS rescore
  57. 2026-05-24 16:43 UTCEPSS rescore

Publicly available exploits

(2 references)

Public exploit code is referenced for this CVE (1 Metasploit module, 1 Exploit-DB entry). Defenders should treat patch urgency accordingly.

  • Exploit-DBEDB-25137✓ verified
    Published May 1, 2013

    WordPress Plugin W3 Total Cache - PHP Code Execution (Metasploit)

    Open source ↗
  • Metasploitexploit/unix/webapp/wp_total_cache_exec✓ verified
    Published Apr 28, 2013

    WordPress W3 Total Cache PHP Code Execution

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2013-2010?
CVE-2013-2010 is a critical vulnerability published on February 12, 2020. WordPress W3 Total Cache Plugin 0.9.2.8 has a Remote PHP Code Execution Vulnerability
When was CVE-2013-2010 disclosed?
CVE-2013-2010 was first published on February 12, 2020, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2013-2010 actively exploited?
CVE-2013-2010 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model classifies it as weaponized: a functional public exploit exists. FIRST EPSS estimates a 74% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2013-2010?
CVE-2013-2010 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2013-2010?
No fix for CVE-2013-2010 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2013-2010

Explore →

Is Your Infrastructure Affected by CVE-2013-2010?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs