Vulnerability 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.
CVSS Score
HIGH
Related Weaknesses (CWE)
References
- https://plugins.trac.wordpress.org/browser/w3-total-cache/tags/2.9.3/Generic_Plu
- https://plugins.trac.wordpress.org/changeset/3495959/w3-total-cache
- https://www.wordfence.com/threat-intel/vulnerabilities/id/a65eb62d-847b-4f3a-848
FAQ
What is CVE-2026-5032?
CVE-2026-5032 is a vulnerability with a CVSS score of 7.5 (HIGH). 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 processin...
How severe is CVE-2026-5032?
CVE-2026-5032 has been rated HIGH with a CVSS base score of 7.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-5032?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.