Is a3 Lazy Load safe to use?

Laskyr does not give safety verdicts. No known unpatched vulnerabilities in the latest version (2.7.9). As of 2026-11-04. 2 issues are on record for older versions; version 2.7.7 or newer fixes all of them that state a fix. Keep a3 Lazy Load on the latest version (2.7.9) and remove it if you do not use it.

Which versions of a3 Lazy Load are vulnerable?

Known issues on record (newest first): Stored cross-site scripting (XSS) (2.7.6 and older, fixed in 2.7.7); Stored cross-site scripting (XSS) (2.7.5 and older, fixed in 2.7.6). The full list with sources is on this page.

What is the latest version of a3 Lazy Load?

2.7.9, according to wordpress.org (last updated 2026-07-08). It has 80,000+ active installs.

What should I do if my a3 Lazy Load is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update a3-lazy-load). If you cannot update right away, deactivate it until you can. If you think the site was already attacked, run a free scan at https://laskyr.com/scan.

Plugins · a3-lazy-load · data as of 2026-11-04

Is a3 Lazy Load safe? Known vulnerabilities and latest version

Latest version: 2.7.9
Last updated: 2026-07-08
Active installs: 80,000+
Known issues on record: 2
Unpatched in latest: 0
Tested up to WP: 7.0.8

Use a3 Lazy Load for images, videos, iframes that are not lazy loaded by WordPress core. Instantly improve your sites load time and dramatically impro … — by Steve Truman

What to do

Update to the latest version (2.7.9). Anything older than 2.7.7 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
If you cannot update right away, deactivate it until you can.
Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.

With WP-CLI: wp plugin get a3-lazy-load --field=version shows what you run; wp plugin update a3-lazy-load updates it.

Check your version

Known vulnerabilities

2 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

medium 6.4 CVE-2026-6427 · published 2026-05-28

Stored cross-site scripting (XSS) in a3 Lazy Load (2.7.6 and older)

Affected: 2.7.6 and older
Fixed in: 2.7.7 *
Access needed (per CVSS): Needs a low-level account (e.g. subscriber)
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

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.

NVD CVE-2026-6427 Wordfence advisory Code change (fix)Plugin source

medium 6.4 CVE-2025-9873 · published 2025-12-13

Stored cross-site scripting (XSS) in a3 Lazy Load (2.7.5 and older)

Affected: 2.7.5 and older
Fixed in: 2.7.6 *
Access needed (per CVSS): Needs a low-level account (e.g. subscriber)
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

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.

NVD CVE-2025-9873 Wordfence advisory Code change (fix)Plugin source

Recent activity

2026-07-08 — latest release on wordpress.org (2.7.9).
2026-05-28 — Stored cross-site scripting (XSS) disclosed (CVE-2026-6427), fixed in 2.7.7.
2025-12-13 — Stored cross-site scripting (XSS) disclosed (CVE-2025-9873), fixed in 2.7.6.

Free. We check the CVE feeds every day and email you only when a new issue for a3 Lazy Load (a3-lazy-load) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: Cross-site scripting (XSS) (2)

Where this data comes from

Version, last update, installs: wordpress.org/plugins/a3-lazy-load (Plugins API), fetched 2026-11-04.
Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.

Badge for your site or docs (states facts with a date, not a verdict):

<a href="https://laskyr.com/plugins/a3-lazy-load"><img src="https://laskyr.com/plugins/a3-lazy-load/badge.svg" alt="a3 Lazy Load vulnerability status"></a>

← Check another plugin · Free hacked-site scan