Live › vulnerability › CVE-2026-111254
The W3 Total Cache WordPress plugin fails to sanitize the 'comment' parameter, so stored script injected through it runs in the browser of any user who opens an affected page. An unauthenticated attacker who holds a previously approved commenter identity can plant the script.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-31 07:34 UTC. All times on this page are UTC.
Sites running W3 Total Cache 2.10.7 or earlier are exposed only when the Pro license has lapsed while REST caching was enabled and Disk Enhanced page caching is still configured. The attacker also needs a commenter identity that a site admin has approved. Sites that do not run the plugin, or that do not match this configuration, can skip it.
No product ranges from the sources yet.
2.10.7 or earlier2.10.7; the exact fixed version is unknown from the sourcesEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-111254")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.