dbcve.org
Responsive LightboxWordPress extension · Dfactory

CVE-2023-49174

MEDIUM · 5.4 CVSS v3.1 Published 2023-12-15
Fix available
A fix is available. Upgrade to 2.4.6 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in dFactory Responsive Lightbox & Gallery allows Stored XSS.This issue affects Responsive Lightbox & Gallery: from n/a through 2.4.5.

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

Stored Cross-site Scripting (XSS) vulnerability in the dFactory Responsive Lightbox & Gallery WordPress plugin allows attackers to inject malicious JavaScript through unsanitized user input that is later rendered in web pages without proper output encoding.

MitigationUpdate the Responsive Lightbox & Gallery plugin to a version beyond 2.4.5, or apply proper input sanitization and output encoding to all user-supplied data before rendering in the application.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Responsive LightboxWordPress extension
Affected:< 2.4.6

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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. Locate the Responsive Lightbox plugin directory
    Check if the /wp-content/plugins/responsive-lightbox/ directory exists on the WordPress server filesystem
    Affected if The directory does not exist - the plugin is not installed
  2. Retrieve the installed plugin version
    Open the main plugin file (typically responsive-lightbox.php) in the plugin directory and locate the Version header in the plugin comment block, or query the WordPress database: SELECT option_value FROM wp_options WHERE option_name = 'responsive_lightbox_version'
    Affected if The version returned is less than 2.4.6 (for example, 2.4.5, 2.4.4, etc.)
  3. Confirm the plugin is activated
    Check the WordPress admin under Plugins > Installed Plugins to verify Responsive Lightbox & Gallery shows as 'Active', or query: SELECT option_value FROM wp_options WHERE option_name = 'active_plugins' AND option_value LIKE '%responsive-lightbox%'
    Affected if The plugin appears in the active plugins list - the vulnerable code is executing
  4. Identify plugin settings pages that accept user input
    Access the plugin settings at Settings > Responsive Lightbox (or similar) in the WordPress admin panel and note all fields where user input is saved (such as gallery titles, lightbox captions, or attachment metadata settings)
    Affected if Any settings page accepts text input without visible sanitization warnings - user-supplied data could be stored and rendered unsanitized

If the plugin is installed with a version earlier than 2.4.6 and is currently active, the stored XSS vulnerability is present in the environment.

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
Upgrade available Upgrade to 2.4.6 or later
Fixed in 2.4.6
Interim mitigation

Update the Responsive Lightbox & Gallery plugin to a version beyond 2.4.5, or apply proper input sanitization and output encoding to all user-supplied data before rendering in the application.

Recommended fix High confidence

Responsive Lightbox & Gallery version 2.4.6

  1. 1. Back up your WordPress site before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. 3. Locate 'Responsive Lightbox & Gallery' in the plugin list
  4. 4. If an update to version 2.4.6 is available, click 'Update Now'
  5. 5. Alternatively, manually download version 2.4.6 from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
  6. 6. Verify the update was successful by checking the installed version number

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

Fix this in Responsive Lightbox Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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