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

CVE-2025-12359

MEDIUM · 5.4 CVSS v3.1 Published 2025-11-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/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.5.3 via the 'get_image_size_by_url' function. This is due to insufficient validation of user-supplied URLs when determining image dimensions for gallery items. 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 versions up to 2.5.3 contain an SSRF vulnerability in the get_image_size_by_url function. This function lacks proper validation of user-supplied URLs, allowing authenticated attackers with Author-level or higher permissions to cause the server to make arbitrary HTTP requests to internal or external locations, potentially exposing internal services or facilitating further attacks.

MitigationUpgrade the plugin to version 2.5.4 or later which contains the fix. If immediate patching is not feasible, consider implementing URL allowlist validation at the web server or application level, and temporarily restrict access to gallery management features for lower-privileged users.

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
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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. Confirm plugin installation and version
    Locate the Responsive Lightbox & Gallery plugin in your WordPress installation (typically in wp-content/plugins/responsive-lightbox/) and read the main plugin file header for the Version field, or check the Plugins page in WordPress admin dashboard.
    Affected if The plugin is installed and the reported version is 2.5.3 or lower
  2. Verify authenticated user privileges
    Check your WordPress user database (wp_users table) and user meta (wp_usermeta) for any accounts with the role of Author, Editor, or Administrator, as these roles have the privilege level required to trigger the vulnerable function.
    Affected if There exists at least one user account with Author-level or higher permissions who could access the gallery management features
  3. Identify exposure of the vulnerable endpoint
    Examine the plugin files, specifically looking for the get_image_size_by-url function, and determine if it is reachable via an AJAX endpoint or direct URL parameter that accepts a user-supplied URL for image processing.
    Affected if The get_image_size_by_url function is accessible without additional authentication beyond standard WordPress user authentication, and it accepts URL parameters that could be controlled by an authenticated Author+ user
  4. Review recent access logs for suspicious requests
    Search your web server access logs for requests to WordPress admin-ajax.php or the plugin's AJAX endpoints that include unusual or internal URLs in the parameters, particularly URLs pointing to internal IP addresses (127.0.0.1, 192.168.x.x, 10.x.x.x) or local services.
    Affected if Logs show requests from authenticated users containing internal or unusual URLs passed to the plugin's image processing functions

Your environment is affected if the Responsive Lightbox & Gallery plugin versions 2.5.3 or lower are installed, at least one user with Author-level or higher permissions exists, and the get_image_size_by_url function is accessible to process arbitrary URLs.

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

Upgrade the plugin to version 2.5.4 or later which contains the fix. If immediate patching is not feasible, consider implementing URL allowlist validation at the web server or application level, and temporarily restrict access to gallery management features for lower-privileged users.

Recommended fix Moderate confidence

Responsive Lightbox & Gallery version 2.5.4 or later

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Responsive Lightbox & Gallery' plugin
  4. Click 'Update Now' if an update is available, or manually download and install version 2.5.4 or later from the WordPress plugin repository
  5. Verify the plugin is updated to version 2.5.4 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
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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