LiveActive security incident?Get immediate response
CVE Record

CVE-2026-1307: Ninja Forms <= 3.14.1 - Authenticated (Contributor+) Sensitive Information Disclosure via Block Editor Token

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.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-1307 is a medium-severity sensitive information disclosure issue in the WordPress Ninja Forms plugin through version 3.14.1. An authenticated user with Contributor-level access or higher may be able to obtain an authorization token exposed through the block editor/admin script loading path and use it to view form submissions for arbitrary forms. Those submissions may contain personal or business-sensitive data.

Executive priority

Treat as a near-term remediation item. Prioritize sites that collect sensitive form submissions or allow multiple Contributor+ users. The issue is not currently supported as actively exploited in the provided sources, but the confidentiality impact is high if abused.

Technical view

The vulnerability affects Ninja Forms - The Contact Form Builder That Grows With You for WordPress in versions up to and including 3.14.1. The source bundle attributes the issue to a callback function for the admin_enqueue_scripts action handler in blocks/bootstrap.php. The exposure can disclose an authorization token to authenticated Contributor+ users, enabling access to form submissions outside the user’s intended authorization boundary. CVSS 3.1 score is 6.5 with vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N and CWE-200.

Likely exposure

WordPress sites running Ninja Forms versions up to and including 3.14.1 are the relevant exposure population, especially sites that allow Contributor, Author, Editor, or other non-admin accounts and collect sensitive information through forms. Sites with only trusted administrators and no sensitive submissions have lower practical risk, but the affected version should still be reviewed.

Exploitation context

No active exploitation is supported by the provided bundle. KEV is false, and the bundle does not include a source indicating exploitation in the wild. Exploitation requires an authenticated WordPress account with Contributor-level access or higher; the reported impact is unauthorized viewing of form submissions, not code execution or service disruption.

Researcher notes

Assessment is based only on the supplied CVE source bundle. The bundle includes a Wordfence vulnerability reference and a WordPress plugin Trac changeset, but it does not explicitly provide a fixed version number beyond identifying versions up to and including 3.14.1 as affected. No exploit code, payloads, or active exploitation claims are included.

Mitigation direction

  • Inventory WordPress installations using Ninja Forms and identify any instances running version 3.14.1 or earlier.
  • Check official vendor/plugin guidance and update to a vendor-fixed release newer than the affected range where available; do not assume a specific fixed version from this bundle alone.
  • Restrict Contributor-level and higher WordPress accounts to trusted users only, and remove or downgrade accounts that do not require dashboard/block editor access.
  • Review Ninja Forms submissions for sensitive data exposure risk and consider rotating or minimizing retained sensitive form data where operationally feasible.
  • Review access logs and WordPress user activity for unusual submission access by non-administrative users.

Validation and detection

  • Confirm the installed Ninja Forms version on each WordPress site and flag versions up to and including 3.14.1.
  • After applying vendor guidance or an update, verify that non-admin Contributor-level users cannot access arbitrary Ninja Forms submissions.
  • Review the block editor/admin script behavior for affected pages to confirm sensitive authorization tokens are no longer exposed to Contributor-level users.
  • Validate that role assignments follow least privilege, especially on sites with external contributors or shared editorial accounts.
  • Document findings, remediation date, plugin version after remediation, and any evidence of suspicious access.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-200: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-1307 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2026-1307Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
kstoverNinja Forms – The Contact Form Builder That Grows With You0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-200 · source CWE mapping

Exposure of Sensitive Information to an Unauthorized Actor

Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.