dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-1307

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 Sensitive Information Exposure in all versions up to, and including, 3.14.1 via a callback function for the admin_enqueue_scripts action handler in blocks/bootstrap.php. This makes it possible for authenticated attackers, with Contributor-level access and above, to gain access to an authorization token to view form submissions for arbitrary forms, 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 up to version 3.14.1 contains a sensitive information exposure vulnerability in the admin_enqueue_scripts action handler in blocks/bootstrap.php. Authenticated users with Contributor-level access or higher can exploit a callback function to obtain an authorization token, enabling them to view form submissions from arbitrary forms that may contain sensitive data.

MitigationUpdate the Ninja Forms plugin to a version newer than 3.14.1. Until patched, consider restricting user permissions or monitoring access logs for suspicious form submission access.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Verify Ninja Forms plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Ninja Forms' in the list. Alternatively, check for the /wp-content/plugins/ninja-forms/ directory on the server.
    Affected if Ninja Forms plugin is present in the WordPress installation
  2. Determine installed Ninja Forms version
    In WordPress admin, go to Plugins > Installed Plugins > Ninja Forms and read the version number displayed under the plugin name. Or check the version field in the plugin's main PHP file header.
    Affected if Version is 3.14.1 or lower (any version up to and including 3.14.1)
  3. Confirm vulnerable file exists
    Check if the file /wp-content/plugins/ninja-forms/blocks/bootstrap.php exists on the server. Use a file manager or SSH: ls -la /path/to/wp-content/plugins/ninja-forms/blocks/bootstrap.php
    Affected if The file blocks/bootstrap.php exists in the Ninja Forms plugin directory
  4. Check for Contributor-level or higher user accounts
    In WordPress admin, go to Users > All Users and review the Role column. Look for users with Contributor, Author, Editor, or Administrator roles.
    Affected if Any user account has Contributor-level access or higher (these roles can exploit the flaw)
  5. Review access logs for suspicious form submission access
    Check web server access logs (Apache error.log, Nginx access.log, or WordPress activity logs) for unusual GET/POST requests to form submission endpoints, particularly from lower-privileged user accounts.
    Affected if Logs show form submission data being accessed by users who should not have access to those forms

You are affected if Ninja Forms plugin version 3.14.1 or lower is installed, the blocks/bootstrap.php file exists, and any user with Contributor-level or higher access exists in the WordPress site.

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 Ninja Forms plugin to a version newer than 3.14.1. Until patched, consider restricting user permissions or monitoring access logs for suspicious form submission access.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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