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

CVE-2026-56041

HIGH · 7.1 CVSS v3.1 Published 2026-06-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges 8 weeks old

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
Unauthenticated Cross Site Scripting (XSS) in Responsive Lightbox <= 2.7.6 versions.

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

Unauthenticated Cross Site Scripting (XSS) vulnerability in the Responsive Lightbox WordPress plugin versions 2.7.6 and below allows remote attackers to inject arbitrary JavaScript or HTML into web pages viewed by other users, without requiring authentication.

MitigationUpdate Responsive Lightbox to a version higher than 2.7.6, or implement proper input sanitization and output encoding on the affected parameters.

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

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

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 Responsive Lightbox plugin is installed
    Log into WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'Responsive Lightbox' in the list of active plugins.
    Affected if The plugin appears in the installed plugins list and is activated
  2. Locate the installed version number
    In the WordPress admin under Plugins > Installed Plugins, find the Responsive Lightbox entry. The version number is displayed below the plugin name. Alternatively, open the file /wp-content/plugins/responsive-lightbox/responsive-lightbox.php in a file editor and locate the 'Version:' header in the plugin comment block.
    Affected if Unable to determine version number from plugin list or main plugin file
  3. Compare version against affected range
    Check if the installed version is 2.7.6 or lower. Compare numerically: for example, versions 2.7.0 through 2.7.6 are all affected. Versions above 2.7.6 (such as 2.7.7 or higher) are not affected.
    Affected if Installed version is 2.7.6 or any version lower than 2.7.6 (e.g., 2.7.5, 2.7.0, 2.6.0)
  4. Confirm plugin is accessible to unauthenticated users
    Since this is an unauthenticated XSS vulnerability, the vulnerable code executes for any visitor to the site, not just logged-in users. No special user role or configuration check is required - the mere presence of the vulnerable plugin version makes the attack surface available.
    Affected if Plugin is active and accessible to site visitors without authentication

If the Responsive Lightbox plugin is installed, active, and the version is 2.7.6 or lower, the environment is affected by this unauthenticated XSS vulnerability.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Responsive Lightbox to a version higher than 2.7.6, or implement proper input sanitization and output encoding on the affected parameters.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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