Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessSubmit crafted comment via public form
-
DeliveryModerator approves comment in WordPress
-
ExploitVictim opens page with Shutter lightbox active
-
ExecutionScript executes in victim browser
-
ImpactSession/content compromise in visitor context
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation is not simply remote-unauthenticated despite PR:N: it requires two specific, concrete preconditions stated in the description. First, the site must have 'Shutter' or 'Shutter Reloaded' selected as the active NextGEN Gallery lightbox, since the flaw lives in that lightbox's handling of the 'comment' parameter - sites using a different lightbox are not exploitable. Second, the attacker's injected comment must be approved through WordPress's standard comment moderation workflow before the payload is ever rendered to other visitors, meaning a human moderator step gates every attack and payloads in unapproved or spam-filtered comments never fire. These two factors (non-universal lightbox configuration plus mandatory moderation approval) are the primary real-world limiters and are precisely why the CVSS attack complexity is High; the submission step itself needs no authentication. |
| Impact | This is a medium-severity stored DOM-based XSS (CVSS 5.4, CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N) whose real-world priority is moderate rather than high. The signals are internally consistent and point to a bounded threat: AV:N and PR:N mean the initial comment can be submitted remotely by an unauthenticated attacker, and S:C with C:L/I:L reflects that the payload executes in other visitors' browser context rather than on the server. However, AC:H is well justified by the description's two independent preconditions - the site must have Shutter or Shutter Reloaded selected as the active lightbox, and the malicious comment must pass WordPress's standard moderation workflow before it is ever rendered - both of which are outside the attacker's control. No EPSS score is provided in the input, there is no CISA KEV listing, and the references are plugin source-code lines and the fix changeset rather than a working exploit, so there is no evidence of active or automated exploitation. The vuln.today decision label is 'this_month', consistent with a real but non-emergency issue. Net: a genuine vulnerability worth patching in a normal cycle, not a high-CVSS-but-illusory risk, but its exploitability is materially constrained by moderation and the non-universal lightbox requirement. |
| Exploit ScenarioDerived | On a site using Shutter or Shutter Reloaded as its active NextGEN Gallery lightbox, an unauthenticated attacker submits a gallery comment containing a crafted 'comment' value with a scripting payload. After a moderator approves the comment through WordPress's normal workflow, the payload is rendered unsanitized and executes in the browser of every subsequent visitor who opens the affected page. No public working exploit is identified in the input; the only references are the vulnerable lightbox source lines and the fix changeset. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 31, 2026
Stored DOM-based cross-site scripting in the NextGEN Gallery WordPress plugin (all versions up to and including 4.5.4) lets an unauthenticated attacker place script payloads through the 'comment' parameter that later execute in the browser of any visitor viewing the affected gallery page. Two concrete preconditions gate every attack: the site must have the Shutter or Shutter Reloaded lightbox selected as active (sites using another lightbox are not exposed), and the injected comment must pass WordPress's standard moderation workflow and be approved before it is rendered. Rated CVSS 5.4 with High attack complexity for exactly those reasons; there is no KEV listing and no public exploit identified at time of analysis, and an upstream fix is present in the plugin's trunk changeset 3773860, though a tagged patched release is not independently confirmed in the supplied data.
RemediationAI
An upstream code fix is present in the plugin's trunk changeset 3773860 (https://plugins.trac.wordpress.org/changeset/3773860/nextgen-gallery/trunk/static/Lightbox/shutter/shutter.js), which modifies the Shutter lightbox script; this is a commit-level fix and a tagged release containing it is not independently confirmed in the supplied data, so verify the changelog of the current NextGEN Gallery release before relying on an upgrade, and track the Wordfence advisory (https://www.wordfence.com/threat-intel/vulnerabilities/id/18dc9c01-c849-40c3-87ec-5eebc9660aff?source=cve) for the fixed version once published. Because the flaw is only reachable through the Shutter or Shutter Reloaded lightbox, switching the active lightbox to any other available option removes the vulnerable rendering path until an updated build is deployed - at the cost of losing that specific lightbox's presentation behavior. Tightening comment moderation so that no comment containing HTML or script-bearing markup is approved, and restricting approval rights to trusted moderators, blocks the second precondition, since unapproved or spam-filtered comments never render. Both measures reduce exposure but do not repair the underlying missing output escaping, so applying the upstream fix remains the complete remedy.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is CWE-79 (improper neutralization of input during web page generation), specifically the stored DOM-based variant: untrusted comment content is written into the page and later consumed by client-side JavaScript in the NextGEN Gallery lightbox rather than being neutralized server-side. The vulnerable sink sits in the Shutter and Shutter Reloaded lightbox scripts - the plugin's Trac references point to shutter.js (line 197 and line 67), shutter_reloaded/shutter.js (line 247 and line 75), nextgen_shutter.js (line 120) and nextgen_shutter_reloaded.js (line 118) in the 4.5.4 tag - where the comment value is handled without adequate escaping before being inserted into the DOM. Because execution happens in the DOM at render time, sanitization applied only on the server side during comment submission does not prevent the script from running in the visitor's browser. The CPE entry (cpe:2.3:a:smub:photo_gallery,_sliders,_proofing_and_themes_-_nextgen_gallery) identifies the WordPress plugin itself as the affected product; the vulnerability is configuration-dependent, since it is only reachable when the Shutter or Shutter Reloaded lightbox is active, and the payload only fires after a moderator approves the comment. The CVSS 3.1 vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N records network reachability, no privileges required for the submission step, no user interaction in the metric, scope change because the script runs in the context of the WordPress site, and limited confidentiality and integrity impact; the High attack complexity reflects the mandatory lightbox configuration plus the human moderation approval step rather than any inherent timing or race condition.
Know when Wordpress Plugin gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N
Comment submission is remote and unauthenticated (PR:N), but the required Shutter lightbox config plus mandatory moderation approval make it AC:H; payload runs in other users' browsers, giving S:C with C:L/I:L and no availability impact.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The Photo Gallery, Sliders, Proofing and Themes - NextGEN Gallery plugin for WordPress is vulnerable to Stored DOM-Based Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 4.5.4 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires the site to have Shutter or Shutter Reloaded selected as the active lightbox, and the injected comment must be approved through WordPress's standard moderation workflow before the payload is rendered to other visitors.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
EUVD-2026-114573
GHSA-mmc9-9v24-7pg8
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB