Quick answers
- Is CVE-2026-120019 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-120019 being exploited in the wild.
- How severe is CVE-2026-120019?
- Medium severity, with a CVSS score of 5.4, published 31 October 2026.
- Which products and versions are affected?
- BoldGrid W3 Total Cache up to and including 2.10.7.
- Is there a fix for CVE-2026-120019?
- Yes: fixed in 2.10.8 (implied by commit dated 2026-10-14, prior to disclosure). Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-120019 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-120019?
- Check whether you run BoldGrid W3 Total Cache at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 2.10.8 (implied by commit dated 2026-10-14, prior to disclosure)
Technical details
The plugin is vulnerable to stored cross-site scripting (XSS) via the 'comment' parameter when HTML minify is enabled with the default 'mfunc' entry in the ignored-comment stems list. The vulnerability arises from insufficient input sanitization and output escaping of comment content. Exploitation requires predicting the md5(time()) placeholder namespace by reading the server's HTTP Date header within a specific time window, making it a time-dependent attack requiring network-level access to the target.
Affected products
- BoldGrid W3 Total Cache up to and including 2.10.7
Timeline
- 2026-10-31: disclosed
- 2026-10-14: patched: Fix committed to repository (per-request id for minify placeholders)