CVE-2025-14072VulnerabilityPublished 2 Jan 2026

CVE-2025-14072: Ninja Forms (WordPress plugin) · Improper Authentication

Affects Ninja Forms (WordPress plugin)Source CVE Database V5

Not known to be exploited · CVSS 5.3 Medium · fixed in 3.13.3 : update Ninja Forms (WordPress plugin) when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 3.13.3

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 2 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Ninja Forms	Affected =0	Fixed in–

AI-suggested

1. Immediately update the Ninja Forms plugin to version 3.13.3 or later, where this vulnerability is patched. 2. Restrict REST API access to trusted users or IP ranges using WordPress security plugins or server-level controls to limit exposure. 3. Implement web application firewalls (WAFs) with rules to detect and block suspicious REST API token generation attempts. 4. Regularly audit and monitor REST API logs for unusual access patterns or token generation activities. 5. Enforce the principle of least privilege on WordPress user roles to minimize potential damage if credentials are compromised. 6. Educate site administrators on the importance of timely plugin updates and secure configuration practices. 7. Consider disabling REST API endpoints related to Ninja Forms if not required for site functionality. 8. Conduct periodic security assessments and penetration testing focused on REST API endpoints to identify similar weaknesses.

Description

The Ninja Forms WordPress plugin before 3.13.3 allows unauthenticated attackers to generate valid access tokens via the REST API which can then be used to read form submissions.

Impact

The primary impact of CVE-2025-14072 is the unauthorized disclosure of form submission data, which may include personally identifiable information (PII), payment details, or other sensitive inputs collected via Ninja Forms. For European organizations, this raises significant privacy and compliance concerns, particularly under GDPR regulations that mandate strict protection of personal data. Unauthorized access to form data can lead to data breaches, reputational damage, and potential regulatory fines. Since the vulnerability does not affect data integrity or availability, the risk is confined to confidentiality breaches. However, the ease of exploitation without authentication or user interaction increases the likelihood of opportunistic attacks. Organizations relying on Ninja Forms for customer interactions, surveys, or transactional data collection are at risk of exposing sensitive information to malicious actors. This can undermine trust and lead to secondary attacks such as phishing or identity theft. The medium severity rating suggests that while the threat is serious, it is not critical, but timely remediation is essential to prevent data leakage.

CWE-287Improper Authentication (opens in a new tab)
Class weaknessLikelihood of exploit: HighOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Libraries or Frameworks
Use an authentication framework or library such as the OWASP ESAPI Authentication feature.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
V9.2.3 (opens in a new tab)
Attack patterns
Fake the Source of Data (opens in a new tab)
Utilizing REST's Trust in the System Resource to Obtain Sensitive Data (opens in a new tab)
Session Hijacking (opens in a new tab)
Token Impersonation (opens in a new tab)
Upload a Web Shell to a Web Server (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

wpscan.com/vulnerability/4b19a333-eb19-4903-aa96-1fe871dd0f9f/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 9 Jan 2026, 11:08 UTC

WeaknessesCWE-287

Technical details

References

Community reviews

Related threats