EUVD-2026-40944
GHSA-j235-ccfg-wwpf
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLocate public NEX-Forms form
-
DeliverySubmit _name[] with script payload
-
ExploitPayload stored past wp_kses allow-list
-
ExecutionAdmin/user opens injected page
-
PersistScript executes in victim session
-
ImpactSteal session or perform admin actions
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 requires that a NEX-Forms form exposing the '_name[]' array parameter be reachable by the attacker (the default deployment mode for public forms), and that the attacker submit crafted markup in that parameter. Because the vector is AV:N/AC:L/PR:N/UI:N, no authentication is needed to inject the payload. The limiting factor is that this is STORED XSS: the payload only fires when a victim - typically an administrator reviewing submissions or a visitor loading the injected page - subsequently accesses the affected page, so realized impact depends on someone viewing the stored content. Sites running 9.2.2 or earlier with a publicly accessible NEX-Forms form are exposed; sites on 9.2.3+ or with the plugin disabled are not. |
| Impact | The provided CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N, base 7.2) indicates network-reachable, low-complexity, unauthenticated injection with a scope change reflecting execution in a victim's browser context. No EPSS score, KEV listing, or POC was provided, so exploitation likelihood cannot be quantified from the input; realistically stored XSS in a public-facing form is attractive because the payload can target logged-in administrators. The primary caveat is that impact is bounded to confidentiality and integrity at LOW (C:L/I:L, A:N) - this is client-side script execution, not direct server compromise - so it is a meaningful but not catastrophic issue. The allow-list weakness raises real-world concern because it means the vendor's intended sanitizer does not stop the attack, but note UI:N is the reporter's scoring convention for stored XSS even though a victim must load the injected page. |
| Exploit ScenarioDerived | An unauthenticated attacker submits a NEX-Forms form supplying a malicious '_name[]' array value containing a <script> tag or an on* event handler, which is stored verbatim because NEXForms_allowed_tags() whitelists those constructs. When a site administrator later opens the page or entry that renders the field, the script executes in their authenticated session, enabling session/cookie theft or actions performed as the admin. No public POC was provided, but the low attack complexity and unauthenticated access make exploitation straightforward. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 01, 2026
Stored cross-site scripting in the NEX-Forms - Ultimate Forms Plugin for WordPress (all versions through 9.2.2) lets unauthenticated attackers persist arbitrary JavaScript via the '_name[]' array parameter, which then runs in the browser of any user who views the injected page. The flaw is notable because the plugin's own wp_kses() allow-list (NEXForms_allowed_tags()) deliberately whitelists <script>, <iframe src/srcdoc>, and JS event handlers, so the normal output-filtering layer provides no protection. No public exploit identified at time of analysis; the issue was reported by Wordfence and carries a CVSS 7.2 with a changed scope.
RemediationAI
Vendor-released patch: 9.2.3 - upgrade the NEX-Forms plugin to version 9.2.3 or later, which the plugins.trac changeset (old_path tags/9.2.2, new_path tags/9.2.3) identifies as the remediated release. Consult the Wordfence advisory (https://www.wordfence.com/threat-intel/vulnerabilities/id/da235dea-4884-4e6a-a8b8-65d34f050684?source=cve) for details. If immediate patching is not possible, restrict or disable public/unauthenticated access to NEX-Forms forms that accept the '_name[]' field, place a WAF rule in front of the form-submission endpoint to block <script>, <iframe>, and on* event-handler payloads in that parameter, and audit already-stored submissions/pages for injected markup before an administrator views them - note that WAF filtering can produce false positives on legitimate form input and does not remediate previously stored payloads. Deactivating the plugin until patched fully eliminates exposure at the cost of losing form functionality.
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 affected component is a commercial WordPress form-builder plugin (vendor 'webaways', slug nex-forms-express-wp-form-builder), per CPE cpe:2.3:a:webaways:nex-forms_-_ultimate_forms_plugin_for_wordpress. The root cause is CWE-79 (Improper Neutralization of Input During Web Page Generation): the '_name[]' array parameter is stored without sufficient sanitization and rendered without adequate output escaping. Uniquely, the code path does invoke wp_kses() for filtering, but the custom allow-list function NEXForms_allowed_tags() explicitly permits dangerous elements (<script>, <iframe> with src/srcdoc) and inline event handlers (onClick, onBlur, onChange), effectively neutering the sanitizer. The referenced trac source lines (main.php ~L2660-2903, class.db.php, class.functions.php) trace the storage and rendering flow across plugin versions 9.1.10 and 9.2.2.
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:L/PR:N/UI:N/S:C/C:L/I:L/A:N
Unauthenticated network injection with low complexity (AV:N/AC:L/PR:N); scope change (S:C) since script runs in a victim's browser, with low confidentiality/integrity impact and no availability effect.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The NEX-Forms - Ultimate Forms Plugin for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via '_name[]' Array Parameter in all versions up to, and including, 9.2.2 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. The wp_kses() output filtering pass provides no mitigation because NEXForms_allowed_tags() explicitly permits <script>, <iframe src/srcdoc>, and JS event handlers such as onClick, onBlur, and onChange in its allow-list.
Articles & Coverage 1
Executive ViewAI
The NEX-Forms WordPress plugin (versions ≤9.2.2) contains a stored cross-site scripting vulnerability allowing unauthenticated attackers to inject malicious JavaScript that executes for all site visitors. While no public exploits exist, organizations face immediate risk of customer data theft and session hijacking without a vendor-released patch.
Disable the vulnerable plugin immediately. If operational constraints prevent disabling: (1) Deploy WAF rules blocking script tags, iframe tags, and JavaScript event handlers in the '_name[]' parameter; (2) Restrict form access to authenticated users if operationally feasible; (3) Enable logging and monitoring for injection-pattern requests; (4) Conduct site audit to identify if XSS payloads have already been injected.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
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
Exploit-DB