WordPress security changelog
HIGH CVE-2025-11924 Analyzed

Ninja Forms – The Contact Form Builder That Grows With You: A security weakness

Ninja Forms – The Contact Form Builder That Grows With You is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation.

CVE / CNA score 7.5 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
Ninja Forms – The Contact Form Builder That Grows With You
Plugin slug
ninja-forms
Affected
See vendor advisory
Safe version
See mitigation notes
Published
Dec 17, 2025
Weakness
CWE-639 — Authorization Bypass Through User-Controlled Key

This CVE was published Dec 17, 2025 and is one of 66 known issues for this plugin.

Update, patch or deactivate.

Update Ninja Forms – The Contact Form Builder That Grows With You to a release outside the affected range, or disable and remove it until a fixed version is available.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Technical description

The Ninja Forms – The Contact Form Builder That Grows With You plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to, and including, 3.13.2. This is due to the plugin not properly verifying that a user is authorized before the `ninja-forms-views` REST endpoints return form metadata and submission content. This makes it possible for unauthenticated attackers to read arbitrary form definitions and submission records via a leaked bearer token granted they can load any page containing the Submissions Table block. NOTE: The developer released a patch for this issue in 3.13.1, but inadvertently introduced a REST API endpoint in which a valid bearer token could be minted for arbitrary form IDs, making this patch ineffective.

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

Primary and upstream sources