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

CVE-2026-4379

MEDIUM · 6.4 CVSS v3.1 Published 2026-04-08
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 LightPress Lightbox plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the `group` attribute in the `[gallery]` shortcode in all versions up to, and including, 2.3.4. This is due to the plugin modifying gallery shortcode output to include the `group` attribute value without proper escaping. 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 · moderate confidence

The LightPress Lightbox plugin for WordPress fails to properly escape the `group` attribute value in the `[gallery]` shortcode output, allowing authenticated users with Contributor-level access or higher to inject malicious JavaScript that persists on affected pages and executes when visitors access those pages.

MitigationUpdate the LightPress Lightbox plugin to a version beyond 2.3.4 that includes proper escaping of the `group` attribute, or remove the plugin if no patched version is available.

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. Verify LightPress Lightbox plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'LightPress Lightbox' in the list of active plugins
    Affected if The plugin appears in the list of installed plugins (either active or inactive)
  2. Confirm the installed plugin version
    Click on the plugin name or view the plugin file header (usually lightpress-lightbox.php) to read the Version: field in the plugin metadata
    Affected if The version number displayed is 2.3.4 or lower (the vulnerability affects versions up to and including 2.3.4)
  3. Identify usage of the gallery shortcode with group attribute
    Search your WordPress database (wp_posts table) for posts containing the pattern [gallery group= or [gallery id= by querying the database directly or using a plugin that searches post content
    Affected if Any post or page content contains a [gallery] shortcode that includes a 'group' attribute value, as this is the unescaped parameter
  4. Inspect stored shortcode content for malicious payloads
    Examine the raw content of posts containing [gallery] shortcodes with group attributes - look for JavaScript event handlers (onclick, onerror, onload), script tags, or encoded/escaped characters that may contain XSS payloads
    Affected if The group attribute value contains unsanitized HTML or JavaScript code such as <script>, javascript:, or event handlers like onmouseover

You are affected if the LightPress Lightbox plugin versions 2.3.4 or lower are installed AND any [gallery] shortcode with a group attribute exists in your content that contains unsanitized script or event handler code.

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 LightPress Lightbox plugin to a version beyond 2.3.4 that includes proper escaping of the `group` attribute, or remove the plugin if no patched version is available.

Recommended fix High confidence

Version 2.3.5 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the LightPress Lightbox plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the latest version from wordpress.org/plugins/lightpress-lightbox and upload it via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the plugin is running on version 2.3.5 or higher

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4379 — 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-4379 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