CVE-2026-5032

Published: Apr 02, 2026 Last Modified: Apr 02, 2026
ExploitDB:
Other exploit source:
Google Dorks:
HIGH 7,5
Source: [email protected]
Attack Vector: network
Attack Complexity: low
Privileges Required: none
User Interaction: none
Scope: unchanged
Confidentiality: high
Integrity: none
Availability: none

Description

AI Translation Available

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.

200

Exposure of Sensitive Information to an Unauthorized Actor

Draft
Abstraction: Class Structure: Simple
Common Consequences
Security Scopes Affected:
Confidentiality
Potential Impacts:
Read Application Data
Applicable Platforms
Technologies: Mobile, Not Technology-Specific, Web Based
Likelihood of Exploit: High
View CWE Details
https://plugins.trac.wordpress.org/browser/w3-total-cache/t…
https://plugins.trac.wordpress.org/browser/w3-total-cache/tags/2.9.3/Generic_Pl…
https://plugins.trac.wordpress.org/changeset/3495959/w3-tot…
https://plugins.trac.wordpress.org/changeset/3495959/w3-total-cache
https://www.wordfence.com/threat-intel/vulnerabilities/id/a…
https://www.wordfence.com/threat-intel/vulnerabilities/id/a65eb62d-847b-4f3a-84…