W3 Total Cache <= 2.10.3 - Unauthenticated Stored Cross-Site Scripting via Comment Author Name
Strategic Overview
- Status
- Patched in 2.10.4
- Affected Plugin
- W3 Total Cache
- Affected Version
<= 2.10.3- CVSS
- 7.2High
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2026-18109
At a glance
CVE-2026-18109 is a high-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the W3 Total Cache WordPress plugin, affecting versions <= 2.10.3. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.10.4; sites on affected versions should update now. Disclosed August 2026, reported by daroo.
Vulnerability Overview
The W3 Total Cache plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Author Name in all versions up to, and including, 2.10.3 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. This vulnerability is only exploitable when the Lazy Load Images feature of W3 Total Cache is enabled, as the unsafe re-emission occurs exclusively within the LazyLoad mutator's img tag rewriting step.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Reaching this weakness in W3 Total Cache <= 2.10.3 takes no account at all. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.
Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For W3 Total Cache the fix is 2.10.4: builds <= 2.10.3 are affected, anything from 2.10.4 onward is not.
Remediation
Update to version 2.10.4, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: W3 Total Cache 2.10.4 closes this, and updating the plugin is the step that ends it.
- Firewall
- Login Security
- Alerts
External References
Related records
Same weakness class
- 7.2CVE-2021-24452: W3 Total Cache <= 2.1.4 Reflected Cross-Site Scripting
CVE-2021-24452 - 6.1CVE-2021-24436: W3 Total Cache <= 2.1.3 Reflected Cross-Site Scripting
CVE-2021-24436 - 6.1W3 Total Cache plugin <= 0.9.7.3 Reflected Cross-Site Scripting
- 6.1W3 Total Cache <= 0.9.4.1 Cross-Site Scripting via request_id
Other vulnerabilities in W3 Total Cache
- 9.8CVE-2026-27384: W3 Total Cache <= 2.9.1 Arbitrary Code Execution
CVE-2026-27384 - 9.8CVE-2013-2010: W3 Total Cache <= 0.9.2.8 Remote Code Execution
CVE-2013-2010 - 8.8W3 Total Cache <= 0.9.4.1 Arbitrary File Upload
- 8.8W3 Total Cache <= 0.9.4 CSRF leading to Stored Cross-Site Scripting
- 8.6W3 Total Cache <= 0.9.4 SSRF leading to Host Information Disclosure
- 8.5CVE-2024-12365: W3 Total Cache <= 2.8.1 Server-Side Request Forgery
CVE-2024-12365 - 8.1CVE-2026-57623: W3 Total Cache <= 2.9.4 Arbitrary Code Execution
CVE-2026-57623 - 8.1CVE-2025-9501: W3 Total Cache <= 2.8.12 Command Injection
CVE-2025-9501
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C