# CVE-2013-2010: Code injection in W3 Total Cache Plugin

> Remote attackers can execute arbitrary PHP code on sites using the W3 Total Cache WordPress plugin.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Feb 2020
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-p4q6-rxpw-36xr

## What is CVE-2013-2010?

CVE-2013-2010 is a critical code injection vulnerability in W3 Total Cache Plugin, published on 12 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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

It affects 2 products.


Products: Automattic Wp Super Cache, Boldgrid W3 Total Cache.

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

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

## Is CVE-2013-2010 being exploited?

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

Public exploit code:

- WordPress W3 Total Cache PHP Code Execution (metasploit)
- WordPress Plugin W3 Total Cache - PHP Code Execution (Metasploit) (exploitdb)
- Remote code execution running on w3 total cache cve 2013-2010 (github_poc): https://github.com/spyata123/w3-total-cache-cve-2013-2010

## Other vulnerabilities in W3 Total Cache Plugin

- [CVE-2013-2009](https://insights.sbomify.com/CVE-2013-2009/): Code injection in WP Super Cache Plugin (high 8.8)
- [CVE-2021-24312](https://insights.sbomify.com/CVE-2021-24312/): WP Super Cache < 1.7.3 - Authenticated Remote Code Execution (high 7.2)
- [CVE-2021-24209](https://insights.sbomify.com/CVE-2021-24209/): WP Super Cache < 1.7.2 - Authenticated Remote Code Execution (RCE) (high 7.2)
- [CVE-2013-2008](https://insights.sbomify.com/CVE-2013-2008/): Cross-site scripting in Super Cache Plugin (medium 6.1)
- [CVE-2021-24329](https://insights.sbomify.com/CVE-2021-24329/): WP Super Cache < 1.7.3 - Authenticated Stored Cross-Site Scripting (XSS) (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-2010 is a critical code injection vulnerability in W3 Total Cache Plugin, published on 12 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-2010 exists.

Affected product: W3 Total Cache Plugin. 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-2010/ (Markdown: https://insights.sbomify.com/CVE-2013-2010/index.md)
```

## Sources

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

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