Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as custom-level user
-
DeliverySubmit crafted additional_params to records query
-
ExploitBypass operator allowlist into get_total_records()
-
ExecutionAppend UNION/subquery to unprepared SQL
-
ImpactExtract sensitive database contents
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires an authenticated WordPress account with NEX-Forms 'custom-level' capability or above (per the description) - this is the primary limiting factor and reason for PR:H rather than PR:N. Exploitation targets the records/dashboard query path where the tainted 'additional_params' array is forwarded from get_table_records() to get_total_records() without re-applying the operator allowlist. No user interaction and no non-default configuration are needed beyond the plugin being installed and the attacker holding the required role; all versions up to and including 9.3.0 are affected. Impact is limited to data extraction (read-only confidentiality); no integrity or availability effect is claimed. |
| Impact | This is a genuine SQL injection sink (CWE-89) but a mid-tier priority, not an emergency. The vendor/Wordfence CVSS 3.1 vector (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N, 4.9) is internally consistent with the description: network-reachable but gated behind authenticated access at 'custom-level and above,' which is why PR is elevated and the score stays medium despite C:H. The confidentiality-only impact (I:N/A:N) is appropriate - the description scopes this to extracting sensitive data via appended queries, not modifying data or crashing the DB. No EPSS score, KEV listing, or public POC was provided, so exploitation status is 'no public exploit identified at time of analysis'; however, the changeset diff and the exact vulnerable line references (class.db.php L2954/L2996, class.dashboard.php) effectively serve as a root-cause map that lowers the bar for exploit development. The one thing to verify: whether 'custom-level access' truly warrants PR:H - if NEX-Forms 'custom' capability is easily granted to low-trust users, real-world privilege requirement is closer to PR:L and effective risk is higher than the 4.9 suggests. |
| Exploit ScenarioDerived | An authenticated user holding NEX-Forms 'custom-level' capability (or higher) submits a crafted 'additional_params' value to a records/dashboard query; because get_total_records() does not re-apply the operator allowlist that get_table_records() enforces, the tainted array reaches an unprepared SQL query. The attacker appends a subquery/UNION to exfiltrate password hashes, secret keys, or other data from the WordPress database. No public exploit code is identified, but the published Wordfence changeset and exact source line references materially ease weaponization. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 18, 2026
Authenticated SQL injection in the NEX-Forms - Ultimate Forms Plugin for WordPress (all versions up to and including 9.3.0) allows a user holding the plugin's 'custom-level' capability or above to inject arbitrary SQL through the 'additional_params' parameter and read sensitive data out of the underlying WordPress database. The injection sits in the plugin's records/dashboard query path, where the tainted array is forwarded from get_table_records() into get_total_records() without the operator allowlist being re-applied to the SQL sink, and no user interaction or non-default configuration is required beyond the plugin being installed. Impact is confidentiality-only - an attacker can extract data such as user records and other stored content, but cannot modify or destroy it, and no public exploit code and no confirmed active exploitation were identified at time of analysis; this is a genuine but mid-tier priority issue that is primarily constrained by the high privilege level required.
RemediationAI
There is no confirmed patched release version above 9.3.0 in the available data; however, a code changeset (https://plugins.trac.wordpress.org/changeset?reponame=&old=3679069%40nex-forms-express-wp-form-builder&new=3679069%40nex-forms-express-wp-form-builder, r3679069) touches the plugin repository and appears to be the upstream fix, so this should be read as 'Upstream fix available (PR/commit); released patched version not independently confirmed' - verify the plugin's current release notes before relying on it. Until a patched version is installed, the most effective control is to remove the attack surface entirely: deactivate NEX-Forms on any site where it is not actively needed (trade-off: forms and stored submissions stop rendering). Where the plugin must stay live, strip the 'custom-level' and higher NEX-Forms capabilities from all but a small, trusted administrator set and audit existing role assignments for over-privileged accounts, since the vulnerability is unreachable without that capability (trade-off: legitimate staff lose dashboard/records access). Additionally, block or virtual-patch requests to the plugin's dashboard/records endpoints carrying unexpected characters in 'additional_params' using a WAF or reverse-proxy rule (trade-off: false positives on legitimate filter/sort values), and reduce impact by running WordPress with a database account limited to SELECT/INSERT/UPDATE/DELETE on its own schema so extracted data cannot be escalated. Monitor the vendor plugin page and the Wordfence advisory URL above for a fixed version number and apply it as soon as it is published.
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
NEX-Forms is a WordPress form-builder plugin (vendor webaways) whose administrative dashboard renders submission and record tables through PHP query helpers. The root cause is CWE-89 (Improper Neutralization of Special Elements used in an SQL Command): user-supplied data from the 'additional_params' array is concatenated into a WHERE fragment without use of the WordPress $wpdb->prepare() mechanism or equivalent escaping. The code in includes/classes/class.db.php (approximately lines 2954 and 2996 in the 9.2.5 tag) builds SQL for get_table_records(), which does apply an operator allowlist to its own WHERE fragment - but that allowlist is not enforced on the same tainted 'additional_params' array when it is forwarded to get_total_records(), leaving the second SQL sink unprotected. The callers live in includes/classes/class.dashboard.php (approximately lines 1793, 4133, 4157 and 4393), confirming the vulnerable path is the plugin's dashboard/records listing rather than a public-facing form POST. The CPE string cpe:2.3:a:webaways:nex-forms_-_ultimate_forms_plugin_for_wordpress:*:*:*:*:*:*:*:* covers the affected component, and the CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N vector given here matches the independent assessment: network-reachable and low in attack complexity, but gated behind high privileges (PR:H), which is the main reason the score lands at 4.9 instead of higher.
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:H/UI:N/S:U/C:H/I:N/A:N
Network SQLi with low complexity; PR:H reflects required 'custom-level and above' access (PR:L arguable if that capability is broadly assigned); C:H for data extraction, I:N/A:N as only reads are described.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The NEX-Forms - Ultimate Forms Plugin for WordPress plugin for WordPress is vulnerable to generic SQL Injection via the 'additional_params' parameter in all versions up to, and including, 9.3.0 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with custom-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. The operator allowlist applied by get_table_records() when building its own WHERE fragment is not enforced on the same tainted additional_params array when it is forwarded to get_total_records(), leaving the SQL sink unprotected.
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
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
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-82753
GHSA-7wpp-2mgh-3vfp
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB