CVE-2026-5032
HighW3 Total Cache <= 2.9.3 - Unauthenticated Security Token Exposure via User-Agent Header
Published Apr 2, 2026 · Updated Apr 8, 2026 · Also known as a65eb62d-847b-4f3a-848b-1290e3118c01
Key Facts
Patch in the next maintenance window- CVE-2026-5032 is a high-severity vulnerability (CVSS 7.5 v3.1) affecting W3 Total Cache (wordpress-plugin).
- It is not listed in any known-exploited vulnerabilities catalog. No public exploit code is known.
- EPSS estimates a 2.7% probability of exploitation in the next 30 days.
- Fixed versions are available, including W3 Total Cache 2.9.4.
- Brandefense priority: patch in the next maintenance window, because of its high severity, although no exploitation is known.
CVSS v3.1
7.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS (30-day exploit likelihood)
2.7%
Higher than 85.4% of all scored CVEs
Exploited in the wild
No known
Not in a known-exploited catalog
Public exploit code
None known
Get the full CVE-2026-5032 brief as a PDF
Every affected product and fixed release, exploitation status and a first 24 hours response checklist, emailed within minutes.
Description
The W3 Total Cache plugin for WordPress is vulnerable to information exposure in all versions up to, and including, 2.9.3. This is due to the plugin bypassing its entire output buffering and processing pipeline when the request's User-Agent header contains "W3 Total Cache", which causes raw mfunc/mclude dynamic fragment HTML comments — including the W3TC_DYNAMIC_SECURITY security token — to be rendered in the page source. This makes it possible for unauthenticated attackers to discover the value of the W3TC_DYNAMIC_SECURITY constant by sending a crafted User-Agent header to any page that contains developer-placed dynamic fragment tags, granted the site has the fragment caching feature enabled. With the leaked W3TC_DYNAMIC_SECURITY token, an attacker can craft valid mfunc tags to execute arbitrary PHP code on the server, achieving remote code execution.
Affected Products
2 affected entries in total| Product | Affected versions | Fixed in |
|---|---|---|
| W3 Total Cachewordpress-plugin | See advisory | 2.9.4 |
Patched Releases
W3 Total Cache
2.9.4
Timeline
Publicly disclosed
Apr 2, 2026
Last updated
Apr 8, 2026
Weakness Type
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
- advisoryhttps://www.wordfence.com/threat-intel/vulnerabilities/id/a65eb62d-847b-4f3a-848b-1290e3118c01?source=api-prod
- advisoryhttps://www.wordfence.com/threat-intel/vulnerabilities/id/a65eb62d-847b-4f3a-848b-1290e3118c01?source=api-scan
- otherhttps://plugins.trac.wordpress.org/browser/w3-total-cache/tags/2.9.3/Generic_Plugin.php#L1016
- otherhttps://plugins.trac.wordpress.org/changeset/3495959/w3-total-cache
- otherhttps://www.wordfence.com/threat-intel/vulnerabilities/id/a65eb62d-847b-4f3a-848b-1290e3118c01?source=cve
FAQ
Common Questions.
The W3 Total Cache plugin for WordPress is vulnerable to information exposure in all versions up to, and including, 2.9.3.
Affected: W3 Total Cache (wordpress-plugin). The full list is in the CVE brief.
It is not listed in any known-exploited vulnerabilities catalog.
No, it is not currently listed in the CISA Known Exploited Vulnerabilities catalog.
No public exploit code is known.
Fixed versions are available, including W3 Total Cache 2.9.4.
Brandefense priority: patch in the next maintenance window, because of its high severity, although no exploitation is known.
Is CVE-2026-5032 Running On Your Attack Surface?
Brandefense maps vulnerabilities like this one to your internet-facing assets and tells you exactly where to patch.
Request A Demo