dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-2268

HIGH · 7.5 CVSS v3.1 Published 2026-02-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Ninja Forms WordPress plugin versions up to 3.14.0 has an insecure implementation of the `ninja_forms_merge_tags` filter in repeater fields that resolves `{post_meta:KEY}` merge tags without authorization. Unauthenticated attackers can exploit this via the `nf_ajax_submit` AJAX action to extract arbitrary post metadata including sensitive data like WooCommerce billing emails, API keys, and customer personal information.

MitigationUpdate Ninja Forms to version 3.14.1 or later immediately. Until patched, consider disabling the plugin or restricting access to the nf_ajax_submit AJAX endpoint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Ninja Forms plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and find Ninja Forms. Check the version number displayed, or inspect the plugin header in wp-content/plugins/ninja-forms/includes/index.php
    Affected if The installed version is 3.14.0 or lower (any version up to and including 3.14.0)
  2. Confirm the vulnerable AJAX endpoint is active
    Check if the nf_ajax_submit AJAX action is registered and publicly accessible. This can be verified by examining the plugin's AJAX handlers in includes/AJAX/Controllers/Submit.php or by checking if the action 'wp_ajax_nf_ajax_submit' or 'wp_ajax_nopriv_nf_ajax_submit' is hooked
    Affected if The AJAX endpoint accepts unauthenticated requests (wp_ajax_nopriv_ hook exists)
  3. Identify use of repeater fields with merge tags
    Review active Ninja Forms for any form that uses repeater fields. Check if any field settings or notification emails contain {post_meta:KEY} merge tags, which trigger the vulnerable filter
    Affected if Any form uses repeater fields with {post_meta:...} merge tags in field labels, default values, or notifications

You are affected if Ninja Forms version is 3.14.0 or lower AND the nf_ajax_submit endpoint is exposed to unauthenticated users AND your forms use repeater fields with post_meta merge tags.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Ninja Forms to version 3.14.1 or later immediately. Until patched, consider disabling the plugin or restricting access to the nf_ajax_submit AJAX endpoint.

Recommended fix Moderate confidence

Ninja Forms version 3.14.1 or later (latest stable release)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate Ninja Forms plugin
  4. Check the current version installed
  5. If the installed version is 3.14.0 or earlier, update to the latest available version of Ninja Forms

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2268 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-2268 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data