CVE-2025-14072

MEDIUM5.3/ 10.0
Share:
Published: January 2, 2026 at 06:15 AM
Modified: January 9, 2026 at 01:58 PM
Source: contact@wpscan.com

Vulnerability 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.

CVSS Metrics

Base Score
5.3
Severity
MEDIUM
Vector String
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Weaknesses (CWE)

NVD-CWE-Other
Source: nvd@nist.gov

AI Security Analysis

01 // Technical Summary

Unauthenticated attackers can exploit a vulnerability in the Ninja Forms WordPress plugin to generate valid access tokens, granting them the ability to read sensitive form submissions. This allows for the theft of confidential data and potential further compromise of the targeted WordPress installation.

02 // Vulnerability Mechanism

Step 1: REST API Endpoint Discovery: The attacker identifies the vulnerable REST API endpoint within the Ninja Forms plugin. This endpoint is responsible for generating access tokens. Step 2: Unauthenticated Request: The attacker crafts an unauthenticated request to the identified REST API endpoint. The request may include specific parameters or data that the plugin incorrectly trusts. Step 3: Token Generation: Due to the vulnerability, the plugin processes the unauthenticated request and generates a valid access token. This token is likely returned in the response. Step 4: Token Usage: The attacker uses the generated access token to authenticate subsequent requests to the Ninja Forms REST API. These requests are now authorized as if they were made by a legitimate user. Step 5: Data Exfiltration: The attacker uses the token to access and retrieve sensitive form submission data, including personal information, contact details, and other confidential information.

03 // Deep Technical Analysis

The vulnerability stems from a flaw in the REST API authentication mechanism of the Ninja Forms plugin. Specifically, the plugin fails to properly validate requests, allowing unauthenticated users to generate valid access tokens. This likely involves a missing or flawed authorization check within the token generation process. The root cause is a logic error in how the plugin handles user authentication and authorization when creating access tokens via the REST API. The plugin likely trusts the request parameters without proper validation, leading to the creation of tokens for unauthorized users. This could be due to a missing is_user_logged_in() check or similar authentication validation. The lack of proper input validation on the request parameters used to generate the token is also a contributing factor.

CVE-2025-14072 - MEDIUM Severity (5.3) | Free CVE Database | 4nuxd