CVE-2026-1239

Ninja Forms <= 3.14.1 - Missing Authorization to Unauthenticated Sensitive Information Disclosure via token/refresh REST Endpoint

2026-06-30 17:19
suyoung kim(AhnLab)

Strategic Overview

Status
Patched in 3.14.2
Affected Plugin
Ninja Forms – The Contact Form Builder That Grows With You
Affected Version
<= 3.14.1
CVSS
7.5High
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2026-1239
View all Ninja Forms – The Contact Form Builder That Grows With You vulnerabilities

At a glance

CVE-2026-1239 is a high-severity Missing Authorization vulnerability in the Ninja Forms WordPress plugin, affecting versions <= 3.14.1. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 3.14.2; sites on affected versions should update now. Disclosed June 2026, reported by suyoung kim(AhnLab).

Vulnerability Overview

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 Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality.

CWE-862: Missing Authorization

Reaching this weakness in Ninja Forms <= 3.14.1 takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Ninja Forms the fix is 3.14.2: builds <= 3.14.1 are affected, anything from 3.14.2 onward is not.

Remediation

Update to version 3.14.2, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Ninja Forms 3.14.2 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-1239https://www.wordfence.com/threat-intel/vulnerabilities/id/973ebafc-85c0-4cc5-b307-2fdb0a4a7577https://nvd.nist.gov/vuln/detail/CVE-2026-1239

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C