Skip to content
Fencer Intel
medium 6.4

CVE-2026-125012 json

Flying Images: Optimize and Lazy Load Images for Faster Page Speed <= 2.4.16 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'post_content' Parameter

published 1h ago modified 55m ago also EUVD-2026-128503

cvss
6.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
—
no EPSS score yet
public exploits
0
none known

Summary

The Flying Images: Optimize and Lazy Load Images for Faster Page Speed plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'post_content' parameter in all versions up to, and including, 2.4.16 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Although wp_kses_post sanitizes post content on save, the payload is kses-legal at save time; the plugin's output-buffer rewrite transforms it into an executable form at render time by overwriting the valueless data-src attribute with the unescaped src value, meaning save-time sanitization provides no effective mitigation.

Is CVE-2026-125012 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by version score vector
CNA 3.1 6.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
NVD 3.1 6.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Affected products

  • gijo Flying Images: Optimize and Lazy Load Images for Faster Page Speed

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.