HomeWordPress vulnerabilitiesLazyLoad Plugin
LazyLoad Plugin vulnerabilities
LazyLoad Plugin has 2 known vulnerabilities in this database. The most recent published record is dated 10 Oct 2026.
- Known vulnerabilities
- 2
- Active installs
- 100,000+
- Latest version
- 2.4.1
- Last updated
- 6 Oct 2026
- Most recent
- 10 Oct 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-100196 | High 7.2 | Up to 2.4.0 | Fixed in a later version (latest 2.4.1) | 2 d ago |
| Cross-site scripting (XSS) CVE-2026-105884 | Medium 6.5 | Up to 2.4.0 | Fixed in a later version (latest 2.4.1) | 5 d ago |
Read the published descriptions
- CVE-2026-100196, 10 Oct 2026
- 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. CVE record
- CVE-2026-105884, 7 Oct 2026
- Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in WP Media Rocket Lazy Load rocket-lazy-load allows Stored XSS.This issue affects Rocket Lazy Load: from n/a through 2.4.0. CVE record
What to do if you run LazyLoad Plugin
If you run LazyLoad Plugin, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new LazyLoad Plugin vulnerabilities
Free. We email you when a new vulnerability is published for LazyLoad Plugin, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.