CVE-2026-100196 json
LazyLoad Plugin <= 2.4.0 - Unauthenticated Stored Cross-Site Scripting via Comment Content
published 2026-10-10 30 d ago modified 2026-10-13 27 d ago also EUVD-2026-96211
- cvss
- 7.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 21%
- public exploits
- 0
- none known
Summary
The LazyLoad Plugin – Lazy Load Images, Videos, and Iframes plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment_content (rendered inline into the page HTML)' parameter in all versions up to, and including, 2.4.0 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. WordPress core's wp_kses_data allow-list does not strip the crafted payload on save because it uses only permitted tags and attributes; the event handler is concealed inside a broken attribute region and is only promoted to a real DOM attribute by the plugin's render-time str_replace transformation. Additionally, a site administrator must approve the crafted comment before the payload is served to other visitors.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 29 d ago
Exploit prediction
0.29% chance of exploitation in the next 30 days, higher than 21% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N |
Affected products
- wp_media LazyLoad Plugin – Lazy Load Images, Videos, and Iframes
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/af1060c6-9247-4059-ad6e-993fb7cee6d4?source=cve
- plugins.trac.wordpress.org /browser/rocket-lazy-load/tags/2.4.0/src/Dependencies/RocketLazyload/Image.php#L118
- plugins.trac.wordpress.org /browser/rocket-lazy-load/tags/2.4.0/src/Dependencies/RocketLazyload/Image.php#L115
- plugins.trac.wordpress.org /browser/rocket-lazy-load/tags/2.4.0/src/Dependencies/RocketLazyload/Image.php#L116
- plugins.trac.wordpress.org /browser/rocket-lazy-load/tags/2.4.0/src/Dependencies/RocketLazyload/Image.php#L70
- plugins.trac.wordpress.org /browser/rocket-lazy-load/tags/2.4.0/src/Subscriber/LazyloadSubscriber.php#L326
- plugins.trac.wordpress.org /browser/rocket-lazy-load/tags/2.4.0/src/Subscriber/LazyloadSubscriber.php#L313
- plugins.trac.wordpress.org /browser/rocket-lazy-load/tags/2.4.0/src/Subscriber/LazyloadSubscriber.php#L82
- wordpress.org /plugins/rocket-lazy-load/
- plugins.trac.wordpress.org /changeset?reponame=&new=3730807%40rocket-lazy-load%2Ftags%2F2.4.1&old=3380138%40rocket-lazy-load%2Ftags%2F2.4
Sources
- CVE List CVE-2026-100196
- NVD CVE-2026-100196
Fencer Vulns 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.