W3 Total Cache <= 2.10.7 - Unauthenticated Stored Cross-Site Scripting via Comment Content Cached as HTML after License Expiry
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
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.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original 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.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- boldgrid W3 Total Cache
through 2.10.7