dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2026-65049

CRITICAL · 9.3 CVSS v3.1 Published 2026-07-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 4 weeks old

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
Ninja Forms plugin version 3.14.8 and prior for WordPress Multisite contains an incorrect authorization vulnerability that allows a subsite Administrator to trigger network-wide deletion of all Ninja Forms data by exploiting a site-scoped capability check combined with unsafe multisite migration defaults. Attackers can send a crafted POST request to the admin-ajax.php endpoint with the nf_delete_all_data action and a per-site nonce to invoke migration routines that unconditionally iterate all blogs via switch_to_blog(), dropping all nf3_* tables and clearing options and transients across every subsite in the network without requiring super-admin or network-admin privileges.

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

Ninja Forms 3.14.8 and prior on WordPress Multisite contains an incorrect authorization vulnerability where a subsite Administrator can exploit a site-scoped capability check to trigger network-wide data deletion. By sending a crafted POST request to admin-ajax.php with the nf_delete_all_data action and a per-site nonce, attackers invoke migration routines that use switch_to_blog() to iterate all blogs and drop all nf3_* tables across every subsite without requiring super-admin privileges.

MitigationUpgrade Ninja Forms to version 3.14.9 or later to patch the authorization flaw; alternatively, disable the plugin on WordPress Multisite installations until the update can be applied.

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
Required
Scope
Changed
Confidentiality
None
Integrity
High
Availability
High

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

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. Confirm WordPress Multisite is enabled
    Check wp-config.php for define( 'MULTISITE', true ); or inspect network admin settings at /wp-admin/network/
    Affected if This vulnerability only affects WordPress Multisite installations; single-site installations are not impacted
  2. Identify installed Ninja Forms version
    Navigate to Plugins > Installed Plugins in WordPress admin, locate Ninja Forms, and note the version number displayed, or inspect the plugin header in wp-content/plugins/ninja-forms/index.php
    Affected if The plugin is vulnerable if installed version is 3.14.8 or any prior version
  3. Verify the vulnerable action exists in the plugin
    Search plugin files (particularly in includes/AJAX/Controllers/ or similar directories) for the string 'nf_delete_all_data' as a registered AJAX action hook
    Affected if If the nf_delete_all_data action is present in the plugin code, the vulnerability exists in that version
  4. Check for unsafe migration code with switch_to_blog()
    Inspect plugin migration or database-related PHP files for switch_to_blog() calls combined with nf3_* table operations or options transients clearing routines
    Affected if If migration code uses switch_to_blog() to iterate across sites and drop nf3_* tables indiscriminately, the vulnerability is present

A user is affected if running WordPress Multisite with Ninja Forms version 3.14.8 or prior where the nf_delete_all_data AJAX action with unsafe switch_to_blog() migration exists in the plugin code.

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

Upgrade Ninja Forms to version 3.14.9 or later to patch the authorization flaw; alternatively, disable the plugin on WordPress Multisite installations until the update can be applied.

Recommended fix Moderate confidence

Ninja Forms latest version (check wordpress.org/plugins/ninja-forms for current stable release - versions after 3.14.8 contain the fix)

  1. 1. Navigate to the WordPress admin dashboard for your Multisite network
  2. 2. Go to the Network Admin > Plugins section
  3. 3. Locate Ninja Forms plugin in the installed plugins list
  4. 4. Check the current installed version - if it is 3.14.8 or prior, an update is required
  5. 5. Update Ninja Forms to the latest available version from the WordPress plugin repository
  6. 6. After updating, verify the version number has changed to confirm the update was successful
  7. 7. Test the nf_delete_all_data functionality (or any migration features) on a test subsite to confirm the authorization fix is working correctly

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-65049 — 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-65049 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