dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-1239

HIGH · 7.5 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 →
84/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 Ninja Forms – The Contact Form Builder That Grows With You plugin for WordPress is vulnerable to unauthorized access of data due to a missing authorization check on the 'ninja-forms-views/token/refresh' REST callback in all versions up to, and including, 3.14.1. This makes it possible for unauthenticated attackers to view form submissions, which could potentially contain sensitive information.

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 Ninja Forms WordPress plugin has a missing authorization check on the 'ninja-forms-views/token/refresh' REST API callback in versions up to 3.14.1. This broken access control allows unauthenticated attackers to directly access form submission data through the REST endpoint without any authentication or authorization validation.

MitigationUpdate to version 3.14.2 or later which should include proper authorization checks. If no patched version is available, disable the plugin or restrict access to the REST endpoint via web server configuration.

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 Ninja Forms plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins > locate Ninja Forms. The version number is displayed below the plugin name. Alternatively, check the plugin header in wp-content/plugins/ninja-forms/readme.txt or the main plugin file for the Version constant.
    Affected if The installed version is 3.14.1 or lower
  2. Identify the REST API endpoint exposure
    Make a GET request to your site's /wp-json/ninja-forms-views/token/refresh endpoint using a tool like curl or browser developer tools. Example: curl -s https://yourdomain.com/wp-json/ninja-forms-views/token/refresh
    Affected if The endpoint responds without requiring authentication (no 401 or 403 error returned)
  3. Test for unauthorized data access
    Send a request to the vulnerable endpoint and examine if it returns form submission data, tokens, or other sensitive information without providing any authentication credentials.
    Affected if The endpoint returns actual data, tokens, or submission content without any auth headers or cookies
  4. Cross-reference version against vulnerability scope
    Compare your confirmed installed version to the affected range: versions up to and including 3.14.1 are vulnerable. Version 3.14.2 contains the fix.
    Affected if Your installed version is 3.14.1 or earlier

You are affected if the Ninja Forms plugin version is 3.14.1 or earlier AND the /wp-json/ninja-forms-views/token/refresh endpoint is accessible without authentication.

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

Update to version 3.14.2 or later which should include proper authorization checks. If no patched version is available, disable the plugin or restrict access to the REST endpoint via web server configuration.

Recommended fix Moderate confidence

Upgrade to Ninja Forms version 3.14.2 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Ninja Forms plugin
  4. Check the current version installed (ensure it is 3.14.1 or lower)
  5. If an update is available, click 'Update Now' to update to the latest version
  6. Alternatively, navigate to Dashboard > Updates and update the Ninja Forms plugin from there
  7. After updating, verify the version number reflects the patched release (3.14.2 or higher)

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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