CVE-2024-12006: The W3 Total Cache plugin for WordPress is vulnerable to unauthorized modification of data due to a missing ca

Q: How do I fix CVE-2024-12006?

w3 total cache: upgrade to 2.8.2. Exact commands for each OS are on this page.

Q: Is CVE-2024-12006 being exploited?

CVE-2024-12006 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2024-12006 affect?

CVE-2024-12006 affects w3 total cache. Severity is medium (CVSS 5.3). The W3 Total Cache plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on several functions in all versions up to, and including, 2.8.1. This makes it possible for unauthenticated attack

Q: How urgent is CVE-2024-12006?

Priority 35/100. Remotely exploitable, no login, no user action

Routine

MEDIUM 5.3REMOTEUPGRADE

CVE-2024-12006 is a medium-severity flaw (CVSS 5.3) affecting w3 total cache. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The W3 Total Cache plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on several functions in all versions up to, and including, 2.8.1. This makes it possible for unauthenticated attackers to deactivate the plugin as well as activate and deactivate plugin extensions.

Why this priority

Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	5.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.5% (top 56%)
CISA exploited list	No
Weakness	CWE-862
Published	2025-01-14
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: boldgrid

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-01-14 07:15 UTCPublished CVE record published
2026-06-17 06:58 UTCUpdated Record last modified

boldgrid w3 total cache UPGRADE

Affected: < 2.8.2

Fixed in: 2.8.2

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy w3-total-cache || rpm -q w3-total-cache || w3-total-cache --version

2. UPGRADE to 2.8.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade w3-total-cache

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade w3-total-cache

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-12006?

w3 total cache: upgrade to 2.8.2. Exact commands for each OS are on this page.

Is CVE-2024-12006 being exploited?

CVE-2024-12006 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-12006 affect?

CVE-2024-12006 affects w3 total cache. Severity is medium (CVSS 5.3). The W3 Total Cache plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on several functions in all versions up to, and including, 2.8.1. This makes it possible for unauthenticated attack

How urgent is CVE-2024-12006?

Priority 35/100. Remotely exploitable, no login, no user action

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2024-12365 HIGH 8.5 UPGRADE The W3 Total Cache plugin for WordPress is vulnerable to unauthorized access of data due to a missing capabili
CVE-2024-12008 MEDIUM 5.3 UPGRADE The W3 Total Cache plugin for WordPress is vulnerable to Information Exposure in all versions up to, and inclu
CVE-2023-5359 LOW 3.7 UPGRADE The W3 Total Cache plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to, and

References

← Back to latest CVEs