Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2013-2010: Remote Code Execution in WordPress W3 Total Cache Plugin 0.9.2.8

Published Feb 12, 2020 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.8Critical · v3.1
EPSS73.9%99th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendors
BoldgridAutomattic
IdentifiersCVE-2013-2010CWE-94

A remote PHP code execution vulnerability exists in the WordPress W3 Total Cache Plugin version 0.9.2.8. The vulnerability allows an attacker to execute arbitrary PHP code on the server by exploiting improper input validation or insecure handling of user-supplied data within the plugin.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows remote attackers to execute arbitrary PHP code on the affected server, potentially leading to full compromise of the WordPress installation and underlying system.

Mitigation

If you can’t patch tonight, do this now.

As an interim measure, disable the W3 Total Cache Plugin until a patched version is available. Restrict access to the WordPress admin interface and monitor for suspicious activity.

Remediation

Patch, then assume compromise.

Upgrade to a patched version of the W3 Total Cache Plugin that addresses the code execution vulnerability. Ensure all plugins are kept up to date.

Public exploits

Exploits

2 exploits validated by Mallory's analysis.

View more in app →
wp_total_cache_exec.rbThis repository contains a single Metasploit module (wp_total_cache_exec.rb) that exploits a PHP code injection vulnerability in the WordPress W3 Total Cache plugin (versions <= 0.9.2.8) and WP Super Cache (<= 1.2). The exploit works by posting a specially crafted comment containing a PHP payload using the 'mfunc' macro, which is then executed by the vulnerable plugin. The module can operate with or without authentication, depending on the target's comment settings, and will attempt to find a valid post ID for comment injection. Upon successful exploitation, arbitrary PHP code (the attacker's payload) is executed on the server. The module is operational and provides remote code execution capabilities. The only endpoint is the target WordPress site, which is accessed via HTTP requests to post comments and trigger the payload. The code is written in Ruby and is structured as a standard Metasploit exploit module.Disclosed Apr 17, 2013 · Framework: metasploit · ruby · networkWeaponizedw3-total-cache-cve-2013-2010This repository provides a Python exploit script (w3tc_rce_exploit.py) targeting CVE-2013-2010, a remote code execution vulnerability in the W3 Total Cache plugin for WordPress. The exploit works by sending a crafted comment containing arbitrary PHP code to the vulnerable endpoint '/wp-comments-post.php' on the target site. The script takes two arguments: the target URL and the PHP payload to execute. If successful, the payload is executed on the server, granting the attacker remote code execution capabilities. The repository consists of a single file (README.md) that contains both usage instructions and the full exploit code. The exploit is operational, allowing attackers to specify custom PHP payloads for execution.spyata123 · Disclosed Mar 11, 2025 · python · networkOperational
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
AutomatticWp Super Cacheapplication
BoldgridW3 Total Cacheapplication
FAQ

Frequently asked questions

Is CVE-2013-2010 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2013-2010 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2013-2010?
Yes. Mallory tracks 2 public exploits or proofs of concept for CVE-2013-2010, the earliest disclosed Apr 17, 2013.
Is there a patch for CVE-2013-2010?
Upgrade to a patched version of the W3 Total Cache Plugin that addresses the code execution vulnerability. Ensure all plugins are kept up to date.
What products are affected by CVE-2013-2010?
Boldgrid W3 Total Cache and Automattic Wp Super Cache.
How severe is CVE-2013-2010?
CVE-2013-2010 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 73.9% (99th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.