NextGEN Gallery ≤ 4.4.1: Authenticated RCE Hiding in the Image Renderer (CVE-2026-76010, CVSS 8.8)

Running NextGEN Gallery on your site? Check it against CVE-2026-76010 and CVE-2026-76012 — free.

The free mini-scan checks your live site from the outside and reads the plugin versions it exposes — if your NextGEN Gallery is in one of the affected ranges above, it flags it, alongside TLS/HTTPS basics, security headers, cookie flags, exposed files and Firebase/Supabase backend rules. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

NextGEN Gallery ≤ 4.4.1: Authenticated RCE Hiding in the Image Renderer (CVE-2026-76010, CVSS 8.8)

Galleries feel like the safe end of a WordPress site — pictures, sliders, proofing. But in NextGEN Gallery, one of the most-installed gallery plugins in the ecosystem (300,000+ active installs), the image renderer is a code-execution path. In versions up to and including 4.4.1, CVE-2026-76010 lets an authenticated attacker who owns at least one gallery execute code on the server — and the detail that should worry site owners most is that the access can outlive the permission that granted it: revoke the capability, and the stored gallery-author record can still carry the attacker through the door.

What Happened

CVE-2026-76010 is an authenticated remote code execution vulnerability in the NextGEN Gallery plugin for WordPress, disclosed October 31, 2026 (CNA: Wordfence).

This one is version-checkable, and our scanner checks it: the free mini-scan reads the plugin's public readme and flags a stable tag at or below 4.4.1 as a High finding naming CVE-2026-76010. A site on a newer tag earns no claim either way from this check — because the CVE record names no fixed version, a version above the affected range is silence, not a clean bill of health. The check reads the version only; it never calls render_image, never exercises the flaw, and it cannot see the gallery-ownership precondition — the finding states that precondition, it does not test it.

Am I Affected?

Check wp-admin → Plugins for NextGEN Gallery and its version. At 4.4.1 or below you are in the affected range. Then ask the second question this CVE makes unavoidable: who owns galleries on this site, and who ever did? The exposed population is not "current administrators" — it is every account that owns a gallery, including accounts whose NextGEN capability was granted for a project and later revoked, because the gallery-author fallback can keep that path alive.

What To Do Now

  1. Update NextGEN Gallery to the latest available release today. wordpress.org serves 4.5.5; install the current release and confirm against the vendor changelog. There is no verified "fixed in" version to aim at — latest is the remediation.
  2. Audit gallery owners, not just roles. List every gallery's author, and every low-privilege account that has ever held the 'NextGEN Manage gallery' capability. An owner you cannot name is a finding, not a footnote.
  3. Review uploaded image folders for anything unexpected. A code-execution flaw that travels through an image pipeline leaves its residue in upload directories — files that are not images, or images you cannot tie to a real gallery, are strangers until proven otherwise.
  4. Audit administrator accounts. Users → All Users: every Administrator should be a person you can name. Authenticated RCE is exactly the kind of flaw that gets quietly converted into a persistent admin account.

The Bigger Lesson

Permissions are usually audited as a snapshot — who holds what today. This flaw is a reminder that access is also a history: grants get stored in places a revocation does not reach, and a fallback written to be helpful ("the gallery's author can always manage their gallery") becomes a standing credential. When you revoke access on a site you run, the follow-up question is never just "is the capability gone?" — it is "what did the capability leave behind?" Mass assignment made the same mistake from the other direction: trusting caller-supplied keys to name the fields they may set. Both halves of this CVE are the same lesson — what the code remembers and what it accepts decide who is really inside.

Related: WordPress Hardening for AI-Built Sites — the standing version of this discipline. How to Check If Your Web App Is Hacked — the follow-up pass if the audit finds a stranger.


Running NextGEN Gallery at 4.4.1 or below? Update today, audit your gallery owners, then run the free check at preshipit.com/free-scan — it version-checks this plugin and the rest of your site's announced surface in about a minute.

Check NextGEN Gallery on your own site — free.

Our free WordPress Plugin Vulnerability Checker pulls NextGEN Gallery's current version from wordpress.org and lists the vulnerabilities our scanner checks for — CVE-2026-76010 and CVE-2026-76012 included. No scan, no account.

Open the free plugin checker →

The PreShipIt Brief — a short weekly email for people shipping vibe-coded apps: the week's important vulnerabilities and launch-safety checks, in plain English.

New and free. Double opt-in: we email you a confirmation link before anything else arrives. Unsubscribe any time.

Running NextGEN Gallery on your site? Check it against CVE-2026-76010 and CVE-2026-76012 — free.

The free mini-scan checks your live site from the outside and reads the plugin versions it exposes — if your NextGEN Gallery is in one of the affected ranges above, it flags it, alongside TLS/HTTPS basics, security headers, cookie flags, exposed files and Firebase/Supabase backend rules. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

← Back home · Run a free mini-scan · Scan my app — $29 · See a sample report