Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2024-12008: The W3 Total Cache plugin for WordPress is vulnerable to Information Exposure in all versions up to, and inclu

44
This month
MEDIUM 5.3REMOTEUPGRADE

CVE-2024-12008 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 Information Exposure in all versions up to, and including, 2.8.1 through the publicly exposed debug log file. This makes it possible for unauthenticated attackers to view potentially sensitive information in the exposed log file. For example, the log file may contain nonce values that can be used in further CSRF attacks. Note: the debug feature must be enabled for this to be a concern, and

Why this priority

  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score5.3 (Medium)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance2.4% (top 16%)
CISA exploited listNo
WeaknessCWE-200
Published2025-01-14
Last modified2026-06-17
Publisher (CNA): Wordfence · Vendor: boldgrid

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

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.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

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-12008?

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

Is CVE-2024-12008 being exploited?

CVE-2024-12008 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-12008 affect?

CVE-2024-12008 affects w3 total cache. Severity is medium (CVSS 5.3). The W3 Total Cache plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 2.8.1 through the publicly exposed debug log file. This makes it possible for unauthenticated attackers to view potentially

How urgent is CVE-2024-12008?

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

Software pages

WordPress vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.