Boldgrid W3 Total Cache
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 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 versions and mitigation
From the CVE record and the vendor's references.Affected
- <= 2.9.3
Mitigation
The record names no fix. Check the vendor advisory below.
Timeline
Days relative to CVE publicationFirst public PoC 123 days after publication; not in CISA KEV. First PoC: nuclei template: W3 Total Cache <= 2.9.3 - Unauthenticated Dynamic Security Token Disclosure (nuclei template, 3 Aug 2026).
PoC repositories
Found on GitHub.No PoC repositories found yet.
Other public exploits
Exploit-DB, Metasploit and nuclei count as public PoCs. Exploit-tagged references from the CVE record and NVD are links only. None of these are analysed by us.| Source | Title | Published | Found by us |
|---|---|---|---|
| nuclei template | nuclei template: W3 Total Cache <= 2.9.3 - Unauthenticated Dynamic Security Token Disclosure | 3 Aug 2026 | 14 Nov 2026 |