Skip to main content
CVE-2026-120019VulnerabilityPublished

The W3 Total Cache plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-120019· Medium 5.4

Not known to be exploited · CVSS 5.4 Medium.

Data as of 31 Oct 2026, 10:51 UTC

CVSS 3.1 base score
5.4Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Wordfence)CVSS 3.15.4
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 31 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
boldgridW3 Total CacheAffected
  • <=2.10.7
Fixed in–

AI-suggested

Users should consider disabling HTML Minify or the default 'mfunc' ignored-comment stems as a temporary mitigation. Monitor the vendor's advisory channels for official fixes or updates. Avoid relying on this plugin version in environments where untrusted user input is present until a patch is released.

Description

The W3 Total Cache plugin for WordPress up to and including version 2.10.7 is vulnerable to stored cross-site scripting (XSS) via the 'comment' parameter. This vulnerability arises from insufficient input sanitization and output escaping when HTML Minify is enabled with the default 'mfunc' entry in the ignored-comment stems list. Exploitation requires an attacker to predict a time-based placeholder namespace by reading the server clock from the HTTP Date header. Successful exploitation allows injection of arbitrary scripts that execute when users access the affected pages.

References

Community reviews

Loading reviews…