CVE-2026-50327.5HighCWE-200

CVE-2026-5032: W3 Total Cache <= 2.9.3 - Unauthenticated Security Token Exposure via User-Agent Header

boldgrid · W3 Total Cache

Affected: boldgrid W3 Total Cache · Exploitation: check available, not yet exploited

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

3.2%probability of exploitation in the next 30 days

88th percentile

050100

Higher than 88% of scored CVEs

7.5HighCVSS 3.1

LowMediumHighCrit.

DescriptionCVE.org

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 products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

boldgrid · W3 Total Cacheup to and including 2.9.3

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Check available, not yet exploited. A public nuclei template can confirm it on a system you are authorised to test.
CISA KEV: Not listed
Public check: W3 Total Cache <= 2.9.3 - Unauthenticated Dynamic Security Token Disclosure · nuclei template in projectdiscovery/nuclei-templates
Weakness: Information Exposure · Information Disclosure
Vendor: boldgrid
Published: April 2026
Band: Check available, not yet exploited, April 2026

CoverageNo articles yet

No CyberSIXT article names CVE-2026-5032 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.