Skip to main content
VulnerabilityPublished

CVE-2026-125012: Flying Images: Optimize and Lazy Load Images for Faster Page Speed (WordPress plugin) · Cross-site Scripting

Affects Flying Images: Optimize and Lazy Load Images for Faster Page Speed (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.4 Medium.

Data as of 18 Nov 2026, 09:54 UTC

CVSS 3.1 base score
6.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.16.4
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 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 17 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
gijoFlying Images: Optimize and Lazy Load Images for Faster Page SpeedAffected
  • <=2.4.16
Fixed in–

AI-suggested

Users should restrict contributor-level access and above to trusted users only until a fix is released. Monitor the vendor's advisory channels for updates. Since the vulnerability arises from the plugin's output buffering behavior, disabling or removing the plugin can mitigate the risk.

Description

The Flying Images: Optimize and Lazy Load Images for Faster Page Speed WordPress plugin is vulnerable to stored cross-site scripting (XSS) via the 'post_content' parameter in versions up to and including 2.4.16. Authenticated users with contributor-level access or higher can inject malicious scripts that execute when other users view the affected pages. The vulnerability arises because the plugin modifies post content at render time, bypassing the sanitization performed at save time.

References

Community reviews

Loading reviews…