# CVE-2026-111254: W3 Total Cache Stored Cross-Site Scripting in comments

Source: https://junglewise.ai/threats/cve-2026-111254-the-w3-total-cache-plugin-for-wordpress-is-vulnerable-to-stored  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-31. Updated: 2026-10-31  
License: CC BY 4.0 with a link back

CVE-2026-111254 · Severity: high · CVSS 7.2 · Published 2026-10-31

W3 Total Cache is a WordPress plugin that optimizes website performance through caching. Unauthenticated attackers with a previously approved commenter identity can inject malicious scripts into comments that execute for all users visiting affected pages, potentially enabling account compromise, credential theft, or malware distribution without requiring site administrator action.

Technologies: [BoldGrid W3 Total Cache](https://junglewise.ai/threats/technologies/w3-total-cache). Vendors: [BoldGrid](https://junglewise.ai/threats/vendors/boldgrid).

## Quick answers

**Is CVE-2026-111254 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-111254 being exploited in the wild.

**How severe is CVE-2026-111254?** High severity, with a CVSS score of 7.2, published 31 October 2026.

**Which products and versions are affected?** BoldGrid W3 Total Cache up to and including 2.10.7.

**Is there a fix for CVE-2026-111254?** Yes: fixed in 2.10.8 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-111254 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-111254?** Check whether you run BoldGrid W3 Total Cache at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in 2.10.8 or later

## Technical details

The plugin fails to properly sanitize and escape the 'comment' parameter, allowing stored XSS injection. Exploitation requires specific preconditions: a Pro license must have been active with REST caching enabled but is now inactive, while Disk Enhanced page caching remains configured, and the attacker must hold an approved commenter identity. Successful exploitation results in arbitrary script execution in browsers of all users viewing the affected comments, and a fix is available in version 2.10.8 or later.

## Affected products

- BoldGrid W3 Total Cache up to and including 2.10.7

## Timeline

- 2026-10-31: disclosed
- 2026-10-16: patched: Fix committed on this date via PR #55

## References

- [https://github.com/BoldGrid/w3-total-cache/commit/7168b0d7cc80e827ad234a0428ab3ecdbef3c107](https://github.com/BoldGrid/w3-total-cache/commit/7168b0d7cc80e827ad234a0428ab3ecdbef3c107)
- [https://plugins.trac.wordpress.org/browser/w3-total-cache/tags/2.10.7/Licensing_Plugin_Admin.php](https://plugins.trac.wordpress.org/browser/w3-total-cache/tags/2.10.7/Licensing_Plugin_Admin.php)

## Related threats

- [W3 Total Cache stored cross-site scripting in minify](https://junglewise.ai/threats/cve-2026-120019-the-w3-total-cache-plugin-for-wordpress-is-vulnerable-to-stored)
- [W3 Total Cache unauthenticated path traversal](https://junglewise.ai/threats/cve-2026-66695-w3-total-cache-unauthenticated-path-traversal)
- [BoldGrid W3 Total Cache directory traversal in setupSources](https://junglewise.ai/threats/cve-2026-9282-boldgrid-w3-total-cache-directory-traversal-in-setupsources)
- [BoldGrid W3 Total Cache arbitrary code execution](https://junglewise.ai/threats/cve-2026-57623-boldgrid-w3-total-cache-arbitrary-code-execution)
- [BoldGrid W3 Total Cache broken access control](https://junglewise.ai/threats/cve-2026-39595-boldgrid-w3-total-cache-broken-access-control)