{"id":"CVE-2026-100196","url":"https://www.cyber-defence.io/tools/cve/CVE-2026-100196","generatedAt":"2026-10-28T06:34:51.939Z","title":"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…","description":"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.","published":"2026-10-10T07:16:40.000Z","lastModified":"2026-10-13T13:29:13.000Z","status":"Deferred","sourceIdentifier":"security@wordfence.com","cvss":{"version":"3.1","score":7.2,"severity":"HIGH","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N"},"cwe":["CWE-79"],"affected":[],"epss":{"score":0.00292,"percentile":0.21679,"date":"2026-10-27","history":[{"date":"2026-10-10","score":0.00292,"percentile":0.20068}]},"kev":{"listed":false},"exploits":{"count":0,"verified":false,"firstPublished":null,"source":"Exploit-DB (https://gitlab.com/exploit-database/exploitdb)","entries":[]},"verdict":{"level":"high","text":"High impact if exploited, but EPSS currently rates exploitation as unlikely (0.29%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit."},"changes":[{"kind":"new","label":"New CVE","at":"2026-10-10T07:16:40.000Z","detail":{"score":"7.2","severity":"HIGH","publishedAt":"2026-10-10T07:16:39.833Z"},"summary":"New CVE, high severity (CVSS 7.2)."}],"references":[{"url":"https://plugins.trac.wordpress.org/browser/rocket-lazy-load/tags/2.4.0/src/Dependencies/RocketLazyload/Image.php#L115","source":"security@wordfence.com"},{"url":"https://plugins.trac.wordpress.org/browser/rocket-lazy-load/tags/2.4.0/src/Dependencies/RocketLazyload/Image.php#L116","source":"security@wordfence.com"},{"url":"https://plugins.trac.wordpress.org/browser/rocket-lazy-load/tags/2.4.0/src/Dependencies/RocketLazyload/Image.php#L118","source":"security@wordfence.com"},{"url":"https://plugins.trac.wordpress.org/browser/rocket-lazy-load/tags/2.4.0/src/Dependencies/RocketLazyload/Image.php#L70","source":"security@wordfence.com"},{"url":"https://plugins.trac.wordpress.org/browser/rocket-lazy-load/tags/2.4.0/src/Subscriber/LazyloadSubscriber.php#L313","source":"security@wordfence.com"},{"url":"https://plugins.trac.wordpress.org/browser/rocket-lazy-load/tags/2.4.0/src/Subscriber/LazyloadSubscriber.php#L326","source":"security@wordfence.com"},{"url":"https://plugins.trac.wordpress.org/browser/rocket-lazy-load/tags/2.4.0/src/Subscriber/LazyloadSubscriber.php#L82","source":"security@wordfence.com"},{"url":"https://plugins.trac.wordpress.org/changeset?reponame=&new=3730807%40rocket-lazy-load%2Ftags%2F2.4.1&old=3380138%40rocket-lazy-load%2Ftags%2F2.4.0","source":"security@wordfence.com"},{"url":"https://wordpress.org/plugins/rocket-lazy-load/","source":"security@wordfence.com"},{"url":"https://www.wordfence.com/threat-intel/vulnerabilities/id/af1060c6-9247-4059-ad6e-993fb7cee6d4?source=cve","source":"security@wordfence.com"}],"sources":{"nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-100196","epss":"https://www.first.org/epss/","kev":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","exploitdb":"https://www.exploit-db.com/"},"licence":"CC BY 4.0 — link back to the CVE Explorer if you publish the results; upstream data remains subject to its own terms."}