CVE-2025-11924
Unknown Unknown - Not Provided
Insecure Direct Object Reference in Ninja Forms Plugin Allows Data Exposure

Publication date: 2025-12-17

Last updated on: 2025-12-17

Assigner: Wordfence

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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-12-17
Last Modified
2025-12-17
Generated
2026-05-06
AI Q&A
2025-12-17
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
wordpress ninja_forms 3.13.2
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-639 The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability is an Insecure Direct Object Reference (IDOR) in the Ninja Forms WordPress plugin up to version 3.13.2. It occurs because the plugin does not properly verify user authorization before allowing access to the 'ninja-forms-views' REST endpoints, which return form metadata and submission content. As a result, unauthenticated attackers can read arbitrary form definitions and submission records if they have a leaked bearer token and can load any page containing the Submissions Table block. A patch was released in version 3.13.1, but it was ineffective because it introduced a REST API endpoint that allowed minting valid bearer tokens for arbitrary form IDs.


How can this vulnerability impact me? :

This vulnerability can lead to unauthorized disclosure of sensitive form data and submission records. Attackers can access private information submitted through forms without authentication, potentially exposing personal or confidential data. This can result in privacy breaches and loss of trust in the affected website.


What immediate steps should I take to mitigate this vulnerability?

To mitigate this vulnerability, immediately update the Ninja Forms plugin to a version later than 3.13.2 where the issue is patched. Avoid using versions up to and including 3.13.2, as they contain insecure direct object reference flaws allowing unauthorized access to form data. Additionally, review and restrict access to REST API endpoints related to ninja-forms-views and bearer token issuance until a secure patch is confirmed.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart