CVE-2026-5032: W3 Total Cache <= 2.9.3 - Unauthenticated Security Token Exposure via User-Agent Header
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 W3TCDYNAMICSECURITY security token — to be rendered in the page source. This makes it possible for unauthenticated attackers to discover the value of the W3TCDYNAMICSECURITY 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 W3TCDYNAMICSECURITY token, an attacker can craft valid mfunc tags to execute arbitrary PHP code on the server, achieving remote code execution.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-5032?
The severity of CVE-2026-5032 is considered to be high due to potential information exposure risks.
How do I fix CVE-2026-5032?
To mitigate CVE-2026-5032, update the W3 Total Cache plugin to version 2.9.4 or later.
What types of information are exposed by CVE-2026-5032?
CVE-2026-5032 exposes security tokens via the User-Agent header, which can be intercepted by malicious actors.
Is CVE-2026-5032 present in all versions of W3 Total Cache?
CVE-2026-5032 affects all versions of W3 Total Cache up to and including 2.9.3.
Who is affected by CVE-2026-5032 vulnerabilities?
Any WordPress site using W3 Total Cache version 2.9.3 or earlier is vulnerable to CVE-2026-5032.