dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-2300

MEDIUM · 6.4 CVSS v3.1 Published 2026-05-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The BJ Lazy Load WordPress plugin up to version 1.0.9 contains a stored XSS vulnerability in the filter_images() function. The vulnerability stems from improper regex-based HTML processing using preg_replace that fails to correctly handle HTML attribute boundaries when replacing src attributes. This allows content injected within class attribute values to be promoted into actual DOM attributes after processing, enabling script injection.

MitigationUpdate the BJ Lazy Load plugin to version 1.0.10 or later once available. If no patch exists, implement proper HTML attribute boundary validation in the preg_replace pattern and add output escaping when processing lazy-loaded images.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check BJ Lazy Load plugin version
    In WordPress admin, go to Plugins > Installed Plugins > BJ Lazy Load and view the version number. Alternatively, check the main plugin file (bj-lazy-load.php) and look for the Version header in the plugin comment block.
    Affected if The version listed is 1.0.9 or earlier.
  2. Confirm plugin is active
    Verify that the BJ Lazy Load plugin is enabled in WordPress at Plugins > Installed Plugins. The plugin must be active for the vulnerable filter_images() function to process content.
    Affected if The plugin shows as Active and the filter_images function is being called on page content.
  3. Identify vulnerable code presence
    Locate the filter_images() function in the plugin files (typically bj-lazy-load.php or includes/class-bjll.php). Check if it uses preg_replace to process src attributes without proper HTML attribute boundary validation.
    Affected if The filter_images() function exists and contains preg_replace patterns that replace src attributes without validating HTML attribute boundaries (e.g., missing word boundary \b before src=).

You are affected if the BJ Lazy Load plugin is active at version 1.0.9 or earlier and the filter_images() function processes content with the vulnerable regex pattern.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the BJ Lazy Load plugin to version 1.0.10 or later once available. If no patch exists, implement proper HTML attribute boundary validation in the preg_replace pattern and add output escaping when processing lazy-loaded images.

Recommended fix High confidence

Update BJ Lazy Load plugin to version 1.0.10 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the BJ Lazy Load plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to the patched version
  5. 5. Alternatively, download the latest version from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
  6. 6. Verify the update was successful by checking the plugin version

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2300 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-2300 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data