Skip to main content
VulnerabilityPublished Updated

CVE-2026-78471: Autoptimize (WordPress plugin) · Cross-site Scripting

Affects Autoptimize (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.4 Medium.

Data as of 15 Nov 2026, 20:25 UTC

CVSS 3.1 base score
5.4Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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 2 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 15 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
optimizingmattersAutoptimizeAffected
  • <=3.1.15.1
Fixed in–

AI-suggested

Since exploitation requires specific conditions, administrators should review and consider disabling the 'Lazy-load images?' option in Autoptimize if not needed. Additionally, ensure that the w3-total-cache plugin files are fully removed if the plugin is disabled, and monitor comment approvals carefully to prevent malicious comments from being published. Check the vendor advisory or plugin updates regularly for any forthcoming official fixes.

Description

Autoptimize, a WordPress plugin, is vulnerable to stored Cross-Site Scripting (XSS) via the Comment Author Name field in all versions up to and including 3.1.15.1. The vulnerability arises from insufficient input sanitization and output escaping. Exploitation requires multiple conditions: the 'Lazy-load images?' option enabled by an administrator, presence of the w3-total-cache.php file on disk (even if the plugin is disabled), a class named Minify_HTML loaded by another plugin, and approval of the malicious comment by a moderator. This vulnerability allows unauthenticated attackers to inject scripts that execute when users access the affected pages.

References

Community reviews

Loading reviews…