dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-12142

HIGH · 7.2 CVSS v3.1 Published 2026-07-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges Zero-click 7 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The NEX-Forms WordPress plugin suffers from a Stored XSS vulnerability in all versions up to 9.2.2. Unauthenticated attackers can inject arbitrary JavaScript via the '_name[]' array parameter because the NEXForms_allowed_tags() function explicitly permits dangerous elements including <script>, <iframe>, and event handlers (onClick, onBlur, onChange), bypassing the wp_kses() filter. This results in persistent scripts executing whenever users access injected pages.

MitigationUpgrade to a patched version of NEX-Forms when available; until then, consider disabling the plugin or deploying a WAF rule to block malicious input to the '_name[]' parameter.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify NEX-Forms plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'nex-forms' or look in the WordPress admin under Plugins > Installed Plugins for NEX-Forms.
    Affected if The plugin folder 'nex-forms' exists in the plugins directory.
  2. Determine the installed NEX-Forms version
    Open the main plugin file (usually nex-forms/main-class.php or nex-forms/nex-forms.php) and locate the version definition in the plugin header comment, or check the version displayed in the WordPress admin plugin list.
    Affected if The reported version number is 9.2.2 or lower.
  3. Confirm the plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and verify NEX-Forms shows as 'Active', or query the wp_options table for the option_name 'active_plugins' and check if 'nex-forms' is included.
    Affected if The plugin is active and responding to requests.
  4. Identify if form submissions are accepted
    Test whether the '_name[]' parameter is accepted by submitting a test form request to a page containing a NEX-Forms form, or inspect the HTML source of any published NEX-Forms form to confirm the parameter is used in the form markup.
    Affected if Forms with the '_name[]' parameter are published and accepting input.
  5. Inspect database for existing malicious entries
    Query the WordPress database (wp_postmeta or custom tables created by the plugin) for any stored '_name[]' values containing '<script>', '<iframe>', 'onClick=', 'onBlur=', or 'onChange=' patterns.
    Affected if Database records contain any of these dangerous tags or event handlers in fields associated with the '_name[]' parameter.

You are affected if NEX-Forms plugin version 9.2.2 or lower is installed and active, and the plugin is accepting form submissions via the '_name[]' parameter.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of NEX-Forms when available; until then, consider disabling the plugin or deploying a WAF rule to block malicious input to the '_name[]' parameter.

Recommended fix High confidence

Version 9.2.3 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the NEX-Forms – Ultimate Forms Plugin for WordPress
  4. 4. If an update is available, click 'Update Now' to update to the latest version (9.2.3 or higher)
  5. 5. Alternatively, download the latest version from the WordPress plugin repository and upload it manually

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-12142 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-12142 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data