WordPress plugin · bj-lazy-load
Is BJ Lazy Load safe?
Closed. Replace it.
wordpress.org closed it on May 4, 2026 (security issue), so it gets no more security fixes, and 2 flaws are on record. If your site runs it, move to a maintained alternative.
- Flaws on record
- 2
- High or critical
- 1
- Exploited
- none
Every recorded flaw
- May 12, 2026BJ Lazy Load: Stored Cross-Site ScriptingCVE-2026-2300 · affects up to 1.0.9 · reported by WordfenceMedium 6.4
- Sep 25, 2019The bj-lazy-load plugin before 1.0 for WordPress has Remote File Inclusion.CVE-2015-9415 · fixed in 1.0 · reported by MITRE3.4% oddsHigh 7.5
Records come from the National Vulnerability Database, published by the researchers who found each flaw (Wordfence, Patchstack, WPScan and others); exploited status from CISA; exploit odds from FIRST’s EPSS; current version, installs and closures from wordpress.org, checked daily. Want every plugin on your site checked at once? Run the free website check.
Weekly security brief
The flaws that hit local websites, every Friday.
One short email: what got exploited this week, which WordPress plugins broke, and what to check. Unsubscribe in one click.
Tell us what you're building.
A website, your marketing, a security check, an app, or the thing you've been running out of a spreadsheet for three years. A few lines is plenty.
Not ready to talk yet? Run the free website check and see what Google sees.