The Autoptimize plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the LCP Image to preload metabox
Source GCVE Database
Not known to be exploited · CVSS 6.4 Medium.
Data as of 22 Nov 2026, 03:03 UTC
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 3 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 21 Nov 2026.
What to do
AI-suggested
Users should upgrade beyond version 3.1.13 once a fixed version is released. Until then, restrict contributor-level access to trusted users only and consider disabling the LCP Image to preload metabox feature if possible. Monitor the vendor's advisory channels for updates regarding a patch.
Description
The Autoptimize WordPress plugin contains a stored cross-site scripting (XSS) vulnerability in the LCP Image to preload metabox feature. This affects all versions up to and including 3.1.13. The flaw arises from insufficient sanitization and escaping of user-supplied image attributes in the create_img_preload_tag function. Authenticated users with contributor-level access or higher can inject malicious scripts that execute when other users view the affected pages.