Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessSubmit crafted comment anonymously
-
DeliveryConceal handler in broken attribute to evade wp_kses_data
-
ExploitAdministrator approves pending comment
-
ExecutionRender-time str_replace promotes handler to DOM
-
PersistVisitor loads injected page
-
ImpactArbitrary script executes in victim browser
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires the target WordPress site to accept comments on pages where the LazyLoad plugin (<=2.4.0) applies its lazy-load image/iframe rewriting. The attacker submits an unauthenticated comment whose payload is an event handler hidden inside a malformed ('broken') attribute region so it survives wp_kses_data sanitization on save; the payload only becomes executable because the plugin's render-time str_replace transformation rewrites markup and promotes the handler to a real DOM attribute. Key limiting factor: a site administrator must manually approve the crafted comment before it is served to visitors, so exploitation depends on moderated-comment approval and is not fully self-contained. Execution then occurs for any visitor who loads the affected page. |
| Impact | Severity signals are moderate and partially conflicting. Wordfence assigns CVSS 7.2 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N), driven by network vector, no attacker privileges, and a changed scope (script executes in victims' browsers). However, the vector sets UI:N while the description explicitly states that a site administrator must approve the crafted comment before it is served - this is interaction by a privileged third party, so real-world exploitation is NOT the drive-by, zero-interaction scenario UI:N implies; verify the UI metric with the vendor, as it materially lowers practical risk. No EPSS score, no CISA KEV listing, and no public POC were provided in the input, so there is no public exploit identified at time of analysis and no evidence of active or automatable exploitation. Net: this is a credible stored-XSS issue in a popular plugin, but the mandatory administrator-approval gate and the absence of any exploitation-probability signals make it a patch-in-normal-cycle item rather than an emergency, despite the 7.2 'High' label. |
| Exploit ScenarioDerived | An unauthenticated attacker posts a comment on a WordPress site running the LazyLoad plugin (<=2.4.0), hiding an event handler inside a broken/malformed attribute region that passes WordPress's wp_kses_data allow-list on save. A site administrator later approves the comment; when the plugin's render-time str_replace lazy-load transformation rewrites the markup, the concealed handler is promoted to a live DOM attribute, and the script executes in the browser of every visitor who subsequently views that page. No public exploit code was identified at time of analysis, and low attack complexity (AC:L) means crafting the payload is reliable once the technique is known. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 10, 2026
Stored cross-site scripting in the WordPress plugin LazyLoad Plugin - Lazy Load Images, Videos, and Iframes (rocket-lazy-load) through version 2.4.0 allows unauthenticated commenters to embed a crafted payload in a comment body that survives WordPress's wp_kses_data sanitization and only becomes an executable event handler when the plugin's render-time markup rewriting runs. Any visitor who subsequently loads the affected page can have arbitrary JavaScript executed in their browser, though exploitation is partly constrained because a site administrator must approve the crafted comment before it is rendered to others. There is no confirmed active exploitation (no CISA KEV) and no public exploit code identified at time of analysis; the CVSS 3.1 base score is 7.2 and our assessment adjusts the user-interaction metric to Required (UI:R) to reflect the moderation approval step. The vendor has released a fixed version (2.4.1).
RemediationAI
Upgrade the LazyLoad plugin (rocket-lazy-load) from 2.4.0 or earlier to version 2.4.1, which is the vendor-released fixed version published in the plugin Trac repository (changeset 3730807, new=3730807@rocket-lazy-load/tags/2.4.1, replacing the vulnerable 2.4.0 tag); the Wordfence advisory at wordfence.com/threat-intel/vulnerabilities/id/af1060c6-9247-4059-ad6e-993fb7cee6d4 provides the vulnerability record. If immediate upgrading is not possible, exploitability is already gated by comment moderation: keeping comment approval strictly manual and reviewing pending comments for suspicious attribute fragments before approval blocks the injection step, though this relies on administrator diligence and does not stop a payload submitted by a trusted or auto-approved comment author. Additional compensating controls with trade-offs include temporarily disabling the comments feature on templates where the lazy-load rewriting applies (removes the injection vector but disables user engagement), and adding a Content-Security-Policy that disallows inline event handlers/unsafe-inline for script-src (blocks execution of the promoted handler but can break themes and plugins that rely on inline scripts). Deactivating the plugin entirely removes the vulnerable render-time transformation but sacrifices the lazy-loading performance benefit; note that the vulnerable code is in the plugin's str_replace transformation rather than WordPress core, so core updates alone will not remediate this issue. Because no public exploit code or active exploitation has been confirmed, patching should be prioritized based on exposure (public comment-enabled sites first) rather than treated as an emergency zero-day response.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The issue is a stored cross-site scripting flaw (CWE-79, improperly neutralized input during web page generation) rooted in the interaction between WordPress core's comment sanitization and the plugin's DOM-rewriting logic. On save, comment content passes through WordPress core's wp_kses_data allow-list, which normally strips scripts and disallowed attributes; the crafted payload evades this because it uses only permitted tags and attributes, with the event handler concealed inside a malformed/'broken' attribute region that wp_kses_data does not recognize as a live attribute. The payload is only promoted to a real DOM attribute later, at page render time, by the plugin's str_replace-based lazy-load transformation implemented in src/Dependencies/RocketLazyload/Image.php (around lines 70, 115-118) and src/Subscriber/LazyloadSubscriber.php (around lines 82, 313, 326) in the 2.4.0 tag. In other words, the sanitization and the sink operate at different stages and on different representations of the same markup, so neither layer alone catches the payload. The affected component is the rocket-lazy-load plugin (CPE cpe:2.3:a:wp_media:lazyload_plugin_-_lazy_load_images,_videos,_and_iframes), which rewrites img/iframe markup on the front end to implement lazy loading. Authentication requirements: the CVSS vector carries PR:N, so the injection is unauthenticated; the only prerequisite beyond the vulnerable plugin is that the site accepts comments and that an administrator approves the submitted comment.
Know when Wordpress Plugin gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
Unauthenticated comment submission keeps PR:N and AC:L, but mandatory administrator approval of the comment is third-party interaction, so UI:R rather than UI:N; stored XSS in the visitor's browser gives S:C with C:L/I:L and A:N.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
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.
Executive ViewAI
The WordPress plugin LazyLoad (rocket-lazy-load) up to version 2.4.0 allows a crafted payload to be planted in a comment and later execute in the browser of any visitor to the affected page, giving an attacker a foothold in customer and employee sessions. This primarily affects public-facing websites and their visitors, but because WordPress sessions are commonly the same credentials used to administer content, it can escalate to site takeover, data theft, or distribution of malicious content under the organization's brand. Exploitation requires an administrator to approve the crafted comment, which limits scale but also means a single rushed or automated moderation approval can expose the full audience of that page.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
Remote code execution in the WP Query Console WordPress plugin (versions up to and including 1.0) by Ajit Bohra allows u
EUVD-2026-96211
GHSA-mj58-4j67-93fr
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB