CVE-2026-15446 json
EWWW Image Optimizer <= 8.7.3 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'data-script' Lazy Load Attribute in Post Content
published 2mo ago modified 4h ago also EUVD-2026-62342
- cvss
- 6.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 36%
- public exploits
- 0
- none known
Summary
The EWWW Image Optimizer plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'data-script' Lazy Load Attribute in Post Content in all versions up to, and including, 8.7.3 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. The exploit is achieved by embedding a crafted img element with class='lazyload' and a data-script attribute pointing to an attacker-controlled URL in post content, which the plugin's bundled lazysizes ls.unveilhooks addon then uses to dynamically create and insert a script element into the DOM at page view time.
Patch / fix
Is CVE-2026-15446 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 FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2mo ago
Exploit prediction
0.42% chance of exploitation in the next 30 days, higher than 36% of all scored CVEs (FIRST EPSS, 2026-11-09).
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 |
Affected products
- nosilver4u EWWW Image Optimizer
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- github.com /nosilver4u/ewww-image-optimizer/commit/4488aafaee9212db370a5ed2dcb9bad7912b897d
- wordfence.com /threat-intel/vulnerabilities/id/e8af1fdb-7fec-4bbe-937b-ee2e76cf5c5b?source=cve
- plugins.trac.wordpress.org /browser/ewww-image-optimizer/tags/8.7.3/includes/ls.unveilhooks.js#L116
- plugins.trac.wordpress.org /browser/ewww-image-optimizer/tags/8.7.3/includes/ls.unveilhooks.js#L178
- plugins.trac.wordpress.org /browser/ewww-image-optimizer/tags/8.7.3/classes/class-lazy-load.php#L1679
- plugins.trac.wordpress.org /browser/ewww-image-optimizer/tags/8.7.3/classes/class-lazy-load.php#L496
- plugins.trac.wordpress.org /browser/ewww-image-optimizer/tags/8.6.0/includes/ls.unveilhooks.js#L116
- plugins.trac.wordpress.org /browser/ewww-image-optimizer/tags/8.6.0/includes/ls.unveilhooks.js#L178
- plugins.trac.wordpress.org /browser/ewww-image-optimizer/tags/8.6.0/classes/class-lazy-load.php#L1679
- plugins.trac.wordpress.org /browser/ewww-image-optimizer/tags/8.6.0/classes/class-lazy-load.php#L496
Sources
- CVE List CVE-2026-15446
- NVD CVE-2026-15446
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.