Live › vulnerability › CVE-2026-120019
The W3 Total Cache WordPress plugin up to and including 2.10.7 fails to sanitize the 'comment' parameter, so unauthenticated attackers can store scripts that run in the browser of anyone who opens an affected page. The attack needs HTML Minify enabled with the default 'mfunc' ignored-comment entry, and the attacker must predict a placeholder namespace using the server's Date header.
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 the W3 Total Cache WordPress plugin at version 2.10.7 or earlier with HTML Minify turned on and the default 'mfunc' ignored-comment entry present. Sites without HTML Minify enabled, or with the plugin updated past the affected range, are not exposed by this description.
No product ranges from the sources yet.
wp plugin get w3-total-cache --field=version2.10.7 are affected; the sources do not name a fixed versionEach 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. 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.
This page as .md · .json · in your agent: get_signal("CVE-2026-120019")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.