dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-2479

MEDIUM · 5.0 CVSS v3.1 Published 2026-02-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
56/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 Responsive Lightbox & Gallery plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 2.7.1. This is due to the use of `strpos()` for substring-based hostname validation instead of strict host comparison in the `ajax_upload_image()` function. This makes it possible for authenticated attackers, with Author-level access and above, to make web requests to arbitrary locations originating from the web application, which can be used to query and modify information from internal services.

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 Responsive Lightbox & Gallery WordPress plugin contains an SSRF vulnerability in the ajax_upload_image() function. The plugin uses strpos() to validate hostnames, which only checks for substring matches rather than performing strict hostname comparison. This allows authenticated attackers with Author-level or higher access to bypass validation and make the server perform requests to arbitrary internal or external URLs.

MitigationUpdate the plugin to version 2.7.2 or later which implements proper hostname validation using strict comparison (e.g., parse_url() with exact hostname matching or a whitelist approach). Until patched, limit user permissions for the affected functionality to Administrators only.

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/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. Confirm WordPress installation
    Check for wp-load.php or wp-config.php in the web root directory, or access the site health/status page
    Affected if WordPress is present and the plugin is installed
  2. Identify Responsive Lightbox & Gallery plugin
    Navigate to Plugins > Installed Plugins in WordPress admin, or inspect /wp-content/plugins/ directory for responsive-lightbox folder
    Affected if The plugin is installed and active
  3. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and look at the version number next to Responsive Lightbox & Gallery, or read version.php in the plugin directory
    Affected if Version is earlier than 2.7.2 (vulnerable); version 2.7.2 or later includes the fix
  4. Verify user role access to ajax_upload_image
    Check WordPress user roles: go to Users > All Users and identify accounts with Author, Editor, or Administrator roles. The vulnerability affects Author-level and above.
    Affected if Any user with Author role or higher exists and the plugin is vulnerable
  5. Inspect ajax_upload_image function for weak validation
    Examine the plugin source code in includes/ajax.php or similar file, looking for strpos() used on URL/hostname validation in ajax_upload_image() function
    Affected if strpos() is used for hostname validation (substring check) rather than strict comparison like parse_url() with exact matching

User is affected if WordPress is running with Responsive Lightbox & Gallery plugin versions before 2.7.2 and any user with Author-level or higher access exists, since the ajax_upload_image function uses weak strpos()-based hostname validation.

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 plugin to version 2.7.2 or later which implements proper hostname validation using strict comparison (e.g., parse_url() with exact hostname matching or a whitelist approach). Until patched, limit user permissions for the affected functionality to Administrators only.

Recommended fix High confidence

Upgrade to Responsive Lightbox & Gallery version 2.7.2 or later

  1. 1. Log in to the WordPress admin dashboard with an account having Administrator privileges
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Responsive Lightbox & Gallery' plugin
  4. 4. Check the current installed version (visible in the plugin list)
  5. 5. If the installed version is 2.7.1 or earlier, click 'Update Now' to install the latest patched version
  6. 6. After update completes, verify the new version number in the plugin list
  7. 7. Test that the lightbox and gallery functionality works correctly with the new 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-2479 — 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-2479 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