Findings

CVE-2026-2479

The Responsive Lightbox & Gallery plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 2.7.1.

Published Feb 25, 2026 · updated Jun 17, 2026

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 for substring-based hostname validation instead of strict host comparison in the 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.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Feb 25, 2026 · NIST NVD

    Detected

    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 for substring-based hostname validation instead of strict host comparison in the function. This makes it possible for authenticated attackers, with Author-level access and above, to make web requests to arbitrary locations origin

  2. Jun 17, 2026 · NIST NVD

    Updated

    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 for substring-based hostname validation instead of strict host comparison in the function. This makes it possible for authenticated attackers, with Author-level access and above, to make web requests to arbitrary locations origin

Sources

  • CVE.orgVulnerability recordCVE-2026-2479

    Official CVE identifier

    cve.org
  • NIST NVDVulnerability recordCVE-2026-2479

    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 for substring-based hostname validation instead of strict host comparison in the `ajax_upload_imag

    nvd.nist.gov

References