Vulnary
← back to the feed
Critical· 9.3official fix available

CVE-2026-9059

NextGEN Gallery versions before 4.2.1 are vulnerable to a critical SQL injection attack that can be triggered by an authenticated user with the 'NextGEN Gallery overview' capability. The flaw lies in the 'orderby' parameter of the REST API endpoints '/imagely/v1/galleries' and '/imagely/v1/albums', which fails to properly sanitize input. An attacker could inject arbitrary SQL into the ORDER BY clause, potentially compromising the database.

publishedMay 20, 2026
last modifiedJul 23, 2026
sourcesNVD
severity · cvss
9.3
critical · how bad it is
exploitation · epss
<1%
21th percentile · chance of exploitation in 30 days
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
auto-deletes from the system
counting…on Aug 24, 2026

An official fix is available, so this entry is kept for 30 days and then removed automatically.

01

Who is affected

WordPress sites using the NextGEN Gallery plugin, specifically versions earlier than 4.2.1.

02

Real-world impact

An attacker could run arbitrary SQL commands against the WordPress database, leading to data theft, modification, or deletion, and potentially taking control of the site.

03

Why this severity

The CVSS score of 9.3 reflects the high impact of the vulnerability: it requires authentication but offers high privileges, allows arbitrary SQL injection, and can lead to complete compromise of the database.

04

What to do about it

official fix available
recommended steps
  1. 01Upgrade NextGEN Gallery to version 4.2.1 or later.
  2. 02Restart WordPress or the web server to apply the update.
  3. 03Verify that the REST API endpoints no longer accept malicious 'orderby' values.
interim mitigations
  • Restrict access to the REST API endpoints to trusted users only.
  • Remove or limit the 'NextGEN Gallery overview' capability for non-admin users.
  • Disable the 'orderby' parameter if possible.

NVD description

05

Timeline

  1. May 20, 2026 · May 20, 2026
    Published
    Disclosed and added to the National Vulnerability Database.
  2. Jul 23, 2026 · 12d ago
    Advisory updated
    The NVD record was last revised.
  3. Jul 25, 2026 · 10d ago
    Official fix available
    A vendor patch or mitigation now exists — see the remediation steps above.
06

How it’s attacked

Attack vectorNetwork (remote)
Attack complexityLow
Attack requirementsNone
Privileges requiredHigh
User interactionNone needed
Confidentiality impactHigh
Integrity impactHigh
Availability impactNone
07

References & advisories

(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →