dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-12404

MEDIUM · 5.3 CVSS v3.1 Published 2026-06-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 8 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 authorization bypass in all versions up to, and including, 9.2.2. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to enumerate sequential report IDs and download complete form submission data — including names, email addresses, phone numbers, postal addresses, payment details, and uploaded file paths — for any saved report on the site.

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 up to version 9.2.2 fails to properly verify user authorization when accessing form report endpoints. This allows unauthenticated attackers to exploit predictable (sequential) report IDs to access sensitive form submission data including personal information, payment details, and file paths without any authentication credentials.

MitigationUpdate the NEX-Forms plugin to the latest version beyond 9.2.2 when available. Until then, consider restricting access to form submission endpoints via server-level authentication requirements or web application firewall rules to block unauthenticated access to report data.

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
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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. Confirm NEX-Forms plugin is installed
    Check the WordPress plugins directory for the nex-forms folder, typically at /wp-content/plugins/nex-forms/ or query the WordPress database in wp_options for active plugins containing 'nex-forms'
    Affected if The plugin directory or database entry exists indicating NEX-Forms is present
  2. Identify the installed version number
    Locate the main plugin file (usually nex-forms.php or index.php in the plugin folder) and read the version comment in the file header, or query the WordPress options table for the option_name containing 'nex-forms_version'
    Affected if The version is 9.2.2 or any earlier version (versions higher than 9.2.2 are not affected)
  3. Determine if report endpoints are accessible without authentication
    Attempt a GET request to common report endpoint patterns such as /?nex-forms-preview=report&id=1 or /wp-admin/admin-ajax.php?action=nf_export_report&id=1 without providing any authentication cookies or credentials
    Affected if The endpoint returns form submission data, CSV exports, or JSON containing submission records without requiring login
  4. Check for exposure of sequential report IDs
    Increment the report ID parameter (id=1, id=2, id=3) in the report endpoint URL and observe whether different submission data is returned, confirming predictable ID enumeration is possible
    Affected if Each sequential ID returns different valid submission data, confirming the vulnerability condition

A user is affected if the NEX-Forms plugin version is 9.2.2 or earlier and the report endpoints are reachable without authentication, allowing enumeration of sequential IDs to access submission data.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the NEX-Forms plugin to the latest version beyond 9.2.2 when available. Until then, consider restricting access to form submission endpoints via server-level authentication requirements or web application firewall rules to block unauthenticated access to report data.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-12404 — 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-12404 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