You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
The BJ Lazy Load plugin for WordPress is vulnerable to...
Moderate severity
Unreviewed
Published
May 12, 2026
to the GitHub Advisory Database
•
Updated May 12, 2026
The BJ Lazy Load plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the filter_images() function in all versions up to, and including, 1.0.9. This is due to the use of regex-based HTML processing (preg_replace) that does not properly handle HTML attribute boundaries when replacing src attributes, allowing crafted content inside a class attribute value to be promoted to real DOM attributes after processing. 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.
The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Learn more on MITRE.
CVE ID
CVE-2026-2300
GHSA ID
GHSA-xfmv-2x8g-8rjp
Source code
No known source code
Dependabot alerts are not supported on this advisory because it does not have a package from a supported ecosystem with an affected and fixed version.
The BJ Lazy Load plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the
filter_images()function in all versions up to, and including, 1.0.9. This is due to the use of regex-based HTML processing (preg_replace) that does not properly handle HTML attribute boundaries when replacingsrcattributes, allowing crafted content inside aclassattribute value to be promoted to real DOM attributes after processing. 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.References