Ninja Forms <= 3.14.0 - Unauthenticated Information Disclosure in nf_ajax_submit AJAX Action
Strategic Overview
- Status
- Patched in 3.14.1
- Affected Plugin
- Ninja Forms – The Contact Form Builder That Grows With You
- Affected Version
<= 3.14.0- CVSS
- 7.5High
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2026-2268
At a glance
CVE-2026-2268 is a high-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Ninja Forms WordPress plugin, affecting versions <= 3.14.0. 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.1; sites on affected versions should update now. Disclosed February 2026, reported by johska.
Vulnerability Overview
The Ninja Forms plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.14.0. This is due to the unsafe application of the `ninja_forms_merge_tags` filter to user-supplied input within repeater fields, which allows the resolution of `{post_meta:KEY}` merge tags without authorization checks. This makes it possible for unauthenticated attackers to extract arbitrary post metadata from any post on the site, including sensitive data such as WooCommerce billing emails, API keys, private tokens, and customer personal information via the `nf_ajax_submit` AJAX action.
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-200: Exposure of Sensitive Information to an Unauthorized Actor
Reaching this weakness in Ninja Forms <= 3.14.0 takes no account at all. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.
The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Ninja Forms the fix is 3.14.1: builds <= 3.14.0 are affected, anything from 3.14.1 onward is not.
Remediation
Update to version 3.14.1, 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.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
- 8.8CVE-2021-24163: Ninja Forms Contact Form SendWP Plugin Installation
CVE-2021-24163 - 6.5CVE-2026-1307: Ninja Forms <= 3.14.1 Sensitive Information Disclosure
CVE-2026-1307 - 5.3Ninja Forms Contact Form Email Address Disclosure
- 4.3CVE-2021-24164: Ninja Forms <= 3.4.34 OAuth Connection Key Disclosure
CVE-2021-24164
Other vulnerabilities in Ninja Forms – The Contact Form Builder That Grows With You
- 9.8Ninja Forms Contact Form Code Injection
- 9.8CVE-2019-15025: Ninja Forms Contact Form <= 3.3.21.1 SQL Injection
CVE-2019-15025 - 9.8CVE-2016-1209: Ninja Forms Contact Form… Arbitrary File Upload
CVE-2016-1209 - 9.1CVE-2018-20981: Ninja Forms Insufficient Restrictions during Export
CVE-2018-20981 - 8.8Ninja Forms Contact Form CSRF to Field Import and PHP Object Injection
- 8.8CVE-2020-36174: Ninja Forms Contact Form CSRF to Plugin Installation
CVE-2020-36174 - 8.8Ninja Forms Contact Form <= 2.9.55.1 SQL Injection
- 8.6CVE-2018-16308: Ninja Forms Contact Form <= 3.3.13 CSV Injection
CVE-2018-16308
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C