ANALYSIS · fe2bb260 · PATCHDIFF

Folder Analysisw3-total-cache_2.9.3 → w3-total-cache_2.9.4✓ COMPLETED

Started2026-08-12 00:17:16Z Finished2026-08-12 00:18:14Z Elapsed58s

Vulnerabilities 11

1 CVE article ready PatchLeaks generated full security writeups for the matched CVEs · one per CVE, with affected files linked

CVE-2026-5032

FILTERS 0

STATUS

JUDGE

CVE MATCH

EXTENSION · 1

CWE · 1

OPTIONS

Hide “No vulnerability” Hide unjudged

2/21

All 21 CVE 2 Vuln files 7

SORT

BrowserCache_Plugin.php

AI: 1 vulnerabilities

FUNCTIONS · SOURCE GONE CVE-2026-5032 1 FP

#001

Generic_Plugin.php

AI: 2 vulnerabilities

CWE-346: Origin Validation ErrorFUNCTIONS · SOURCE GONE CVE-2026-5032 1 TP 1 FP

#013

1–2 of 2

⌖

Select a file from the list to inspect its diff and AI analysis.

↑ ↓ to navigate

CVES 1

CVE-2026-5032

Security writeup for CVE-2026-5032

✓ 2 FILES

## The Exploit

An unauthenticated attacker with network access to any WordPress site running W3 Total Cache ≤2.9.3 can leak the `W3TC_DYNAMIC_SECURITY` constant by sending a single GET request with a spoofed User-Agent header. Once leaked, this token permits arbitrary PHP code execution via maliciously crafted `mfunc` tags.

```bash
curl -H "User-Agent: W3 Total Cache" http://target.wordpress.local/
```

The response body will contain unprocessed mfunc/mclude HTML comments in raw form, including the security token visible in page source. An attacker viewing the HTML sees lines like:

```html

```

With the leaked token, the attacker crafts a second request containing a valid mfunc tag that executes arbitrary PHP, achieving remote code execution as the web server user.

## What the Patch Did

**Before**

```php
/**
 * Check User Agent
 */
$http_user_agent = isset( $_SERVER['HTTP_USER_AGENT'] ) ? sanitize_text_field( wp_unslash( $_SERVER['HTTP_USER_AGENT'] ) ) : '';
if ( stristr( $http_user_agent, W3TC_POWERED_BY ) !== false ) {
    return false;
}
```

**After**

```php
// Do not skip output buffering based on User-Agent: the value is client-controlled.
// A request claiming "W3 Total Cache" would previously bypass ob_callback, skipping
// page-cache processing and leaking W3TC_DYNAMIC_SECURITY from unprocessed mfunc/mclude.

return true;
```

The patch removes a `stristr()` check on the `HTTP_USER_AGENT` header that was previously used to conditionally skip the output buffering pipeline. The fix applies no additional validation function; instead, it eliminates the trust boundary violation entirely by removing the User-Agent-based control flow branch. This is the correct approach because HTTP headers are client-spoofable and must never be used as a security enforcement point.

## Root Cause

**CWE-346: Origin Validation Error** (or more broadly, **CWE-807: Reliance on Untrusted Inputs in a Security Decision**).

The vulnerability exists because the plugin checked `$_SERVER['HTTP_USER_AGENT']`—a request header entirely controlled by the client—and used the result to decide whether to invoke output buffering callbacks. When a request arrived with a User-Agent containing the string "W3 Total Cache", the function returned `false`, signalling the caller to skip all output processing. This caused the plugin to emit the page response without invoking `ob_callback()`, which is responsible for post-processing mfunc/mclude tags and stripping the security token before the HTML reaches the browser. By spoofing the User-Agent header, an attacker crossed a trust boundary that should never have existed: they influenced a security-critical decision (whether to process dynamic fragments) using unvalidated input from the network request.

## Why It Works

The load-bearing line is the complete removal of the `stristr()` check and the unconditional `return true;` that follows. If the engineer had simply added a better validation function (e.g., `wp_verify_nonce()` or a server-side token check), the User-Agent header still would not be a suitable input to validate, because validation implies trust after verification—and headers cannot be trusted regardless. The comment added above the fix is equally critical: it explains *why* the check was wrong, preventing future maintainers from re-introducing the same pattern. The engineer understood that some security decisions cannot be hardened; they must be eliminated. A User-Agent-based control flow is architecturally unsound and must be replaced with server-side state (cookies, sessions, or detection logic) that the client cannot forge.

## Hardening Checklist

- **Never use `$_SERVER['HTTP_USER_AGENT']`, `$_SERVER['HTTP_REFERER']`, or other client-supplied headers for security-critical logic.** If you need to vary behavior based on request origin, use server-side sessions (`$_SESSION`), `wp_verify_nonce()` tokens, or cryptographically signed cookies.

- **Audit all output buffering callbacks (`ob_callback`, `ob_start()`) for code paths that skip processing.** Any function that conditionally returns early from a processing pipeline should log the condition and require explicit server-side state (e.g., a transient, option, or capability check) before allowing the bypass.

- **Use WordPress nonces (`wp_create_nonce()`, `wp_verify_nonce()`) for dynamic fragment tokens instead of global constants.** Make each token unique per request or session so that leaking one token does not compromise all subsequent requests.

- **Escape and sanitize all output at the final render point, not earlier in the pipeline.** If mfunc/mclude tags contain sensitive data (security tokens, API keys), do not emit them to the HTML response at any point; process them server-side only.

- **Add integration tests that verify output buffering is *always* invoked for pages containing dynamic fragments,** regardless of User-Agent, Referer, or other headers. A test that sends requests with spoofed User-Agent values and verifies that mfunc tags are never present in raw form in the response would have caught this bug before release.

## References

- https://nvd.nist.gov/vuln/detail/CVE-2026-5032

CVE CVE-2026-5032

PRODUCT Folder Analysis

AFFECTED ≤ w3-total-cache_2.9.3

FIXED IN w3-total-cache_2.9.4

STATUS Generated

Security writeup · CVE-2026-5032

Source files · 2

BrowserCache_Plugin.php Linked

Generic_Plugin.php Linked

↗ NVD