ZeroDay Findings
Sign inSign up

Findings

CVE-2026-2300

The BJ Lazy Load plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the function in all versions up to, and including, 1.0.9.

Published May 12, 2026 · updated Jun 17, 2026

The BJ Lazy Load plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the function in all versions up to, and including, 1.0.9. This is due to the use of regex-based HTML processing ( ) that does not properly handle HTML attribute boundaries when replacing attributes, allowing crafted content inside a 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.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. May 12, 2026 · NIST NVD

    Detected

    The BJ Lazy Load plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the function in all versions up to, and including, 1.0.9. This is due to the use of regex-based HTML processing ( ) that does not properly handle HTML attribute boundaries when replacing attributes, allowing crafted content inside a attribute value to be promoted to real DOM attributes after processing. This mak

  2. Jun 17, 2026 · NIST NVD

    Updated

    The BJ Lazy Load plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the function in all versions up to, and including, 1.0.9. This is due to the use of regex-based HTML processing ( ) that does not properly handle HTML attribute boundaries when replacing attributes, allowing crafted content inside a attribute value to be promoted to real DOM attributes after processing. This mak

Sources

  • CVE.orgVulnerability recordCVE-2026-2300

    Official CVE identifier

    cve.org
  • NIST NVDVulnerability recordCVE-2026-2300

    The BJ Lazy Load plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the function in all versions up to, and including, 1.0.9. This is due to the use of regex-based HTML processing ( ) that does not properly handle HTML attribute b

    nvd.nist.gov

References