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

> Unauthenticated attackers can leak security tokens via User-Agent headers, enabling remote code execution if fragment caching is enabled.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Apr 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-fxg7-rh9m-q77p

## What is CVE-2026-5032?

CVE-2026-5032 is a high-severity vulnerability in boldgrid W3 Total Cache, published on 2 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-5032?


## How do I fix CVE-2026-5032?

No fix has been published for CVE-2026-5032 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-5032 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-5032 exists.

Public exploit code:

- W3 Total Cache <= 2.9.3 - Unauthenticated Dynamic Security Token Disclosure (nuclei): http/cves/2026/CVE-2026-5032.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-5032 and fix it if it is affected.

What it is: CVE-2026-5032 is a high-severity vulnerability in boldgrid W3 Total Cache, published on 2 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-5032 exists.

Affected product: boldgrid W3 Total Cache. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-5032/ (Markdown: https://insights.sbomify.com/CVE-2026-5032/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-5032
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-5032
- OSV: https://osv.dev/vulnerability/CVE-2026-5032

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-5032/
Summaries are generated and may contain mistakes; the official description above is the record.