CVE-2026-120019
Received Received - Intake

Stored XSS in W3 Total Cache WordPress Plugin

Publication date: 2026-10-31

Last updated on: 2026-10-31

Assigner: Wordfence

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. This requires HTML Minify to be enabled with the default 'mfunc' entry present in the ignored-comment stems list, and exploitation depends on the attacker predicting the md5(time()) placeholder namespace by reading the server clock via the HTTP Date response header within the applicable time window.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-31
Last Modified
2026-10-31
Generated
2026-10-31
AI Q&A
2026-10-31
EPSS Evaluated
N/A
NVD
CVE-2026-120019
EUVD
EUVD-2026-114597

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
boldgrid W3 Total Cache 0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

The W3 Total Cache plugin for WordPress has a stored cross-site scripting (XSS) vulnerability due to insufficient input sanitization and output escaping in the 'comment' parameter. This affects versions up to 2.10.7. Unauthenticated attackers can inject malicious scripts into pages, which execute when users access those pages. Exploitation requires HTML Minify to be enabled with a specific 'mfunc' entry in the ignored-comment stems list and depends on the attacker predicting a server-generated placeholder.

Detection Guidance

Check for suspicious scripts in WordPress pages by inspecting page source for injected scripts. Look for unusual comments or minified code containing unexpected payloads. Review server logs for requests with comment parameters containing script tags or unusual characters.

Impact Analysis

Attackers could steal user sessions, inject malicious content into your website, or redirect visitors to harmful sites. This could damage your site's reputation, lead to data breaches, or expose visitors to further attacks. The impact depends on the site's traffic and user interactions.

Compliance Impact

This vulnerability could lead to unauthorized access to user data, violating GDPR's data protection requirements or HIPAA's safeguards for protected health information. If exploited, it may result in data breaches, triggering compliance violations, legal penalties, and reputational harm.

Mitigation Strategies

Update W3 Total Cache to the latest version immediately. Disable HTML Minify feature if enabled. Remove the 'mfunc' entry from the ignored-comment stems list. Monitor your site for any signs of compromise or unusual activity.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-120019. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart