CVE-2026-5032

published 2 Apr 2026 · updated 8 Apr 2026

W3 Total Cache <= 2.9.3 - Unauthenticated Security Token Exposure via User-Agent Header

8.5HighCVSS 7.5EPSS 3%1 public exploits

A public exploit exists; no exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 3%. No fixed version is recorded.

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

Vendors, products and packages with version ranges

VendorProductVersionsFixed
boldgrid<=2.9.3

Exploit evidence

1 public sources

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-5032 severity on Zeptric[![CVE-2026-5032](https://zeptric.io/badge/cve/CVE-2026-5032.svg)](https://zeptric.io/cve/CVE-2026-5032)