Quick answers
- Is CVE-2026-78471 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-78471 being exploited in the wild.
- How severe is CVE-2026-78471?
- Medium severity, with a CVSS score of 5.4, published 2 October 2026.
- Which products and versions are affected?
- Autoptimize up to and including 3.1.15.1.
- Is there a fix for CVE-2026-78471?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-78471 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-78471?
- Check whether you run Autoptimize 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.
Technical details
A stored XSS vulnerability exists in comment author name handling due to insufficient input sanitization and output escaping. The vulnerability requires multiple preconditions: the Lazy-load images option must be enabled, W3 Total Cache must be installed (though disabled), the Minify_HTML class must be loaded by another plugin, and the malicious comment must be approved by a moderator. Once these conditions are met, an unauthenticated attacker can inject arbitrary JavaScript that persists in the database and executes in all users' browsers.
Affected products
- Autoptimize Autoptimize up to and including 3.1.15.1
Timeline
- 2026-10-02: disclosed