HomeWordPress vulnerabilitiesa3 Lazy Load
a3 Lazy Load vulnerabilities
a3 Lazy Load has 2 known vulnerabilities in this database. The most recent published record is dated 28 May 2026.
- Known vulnerabilities
- 2
- Active installs
- 90,000+
- Latest version
- 2.7.9
- Last updated
- 8 Jul 2026
- Most recent
- 28 May 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-6427 | Medium 6.4 | Up to 2.7.6 | Fixed in a later version (latest 2.7.9) | 28 May 2026 |
| Cross-site scripting (XSS) CVE-2025-9873 | Medium 6.4 | Up to 2.7.5 | Fixed in a later version (latest 2.7.9) | 13 Dec 2025 |
Read the published descriptions
- CVE-2026-6427, 28 May 2026
- The a3 Lazy Load plugin for WordPress is vulnerable to Stored Cross-Site Scripting in all versions up to, and including, 2.7.6 This is due to a regex bug in the _filter_videos() method that breaks HTML attribute quoting when processing crafted <video> elements, combined with unescaped output in the admin/views/form-data.php template. An authenticated attacker with Contributor-level access can insert a crafted <video> tag whose src attribute contains an embedded class=" substring that tricks the plugin's class-replacement regex into consuming an attribute-value closing quote. This shifts the HTML5 parser's quote boundary, promoting attacker-controlled text from inside a quoted attribute value into standalone event-handler attributes (autofocus, onfocus). The injected script executes in the browser of any user (including administrators) who views the post. CVE record
- CVE-2025-9873, 13 Dec 2025
- The a3 Lazy Load plugin for WordPress is vulnerable to Stored Cross-Site Scripting in all versions up to, and including, 2.7.5 due to insufficient input sanitization and output escaping on user supplied attributes. 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. CVE record
What to do if you run a3 Lazy Load
If you run a3 Lazy Load, 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 a3 Lazy Load vulnerabilities
Free. We email you when a new vulnerability is published for a3 Lazy Load, 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.