dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2026-0740

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-07
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
High EPSS 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 - File Uploads plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the 'NF_FU_AJAX_Controllers_Uploads::handle_upload' function in all versions up to, and including, 3.3.26. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible. Note: The vulnerability was partially patched in version 3.3.25 and fully patched in version 3.3.27.

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 File Uploads plugin for WordPress lacks proper file type validation in the NF_FU_AJAX_Controllers_Uploads::handle_upload function, allowing unauthenticated attackers to upload any file type to the server. This arbitrary file upload vulnerability enables potential remote code execution.

MitigationUpdate Ninja Forms File Uploads plugin to version 3.3.27 or later to apply the full patch. If immediate update is not possible, consider disabling the file upload functionality or restricting upload endpoints at the web server level.

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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. Verify Ninja Forms File Uploads plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Ninja Forms' with the File Uploads add-on. Alternatively, check the plugins directory for 'ninja-forms-file-upload' folder and read the main PHP file for the 'Version' header.
    Affected if The plugin is installed and active.
  2. Determine the installed version of the File Uploads add-on
    Read the version from the plugin header in the main plugin file (typically ninja-forms-file-upload/ninja-forms-file-upload.php) or view the plugin details in the WordPress plugins admin page.
    Affected if The version number is lower than 3.3.27.
  3. Confirm the file upload functionality is enabled
    Check if the File Uploads feature is active in Ninja Forms settings. Navigate to Ninja Forms > Settings > File Uploads (or equivalent) and verify the module is turned on.
    Affected if File uploads are enabled in the plugin settings.
  4. Verify the upload endpoint is publicly accessible
    Check the site for the presence of the NF_FU_AJAX_Controllers_Uploads endpoint (typically at /wp-admin/admin-ajax.php?action=nf_file_upload or similar). Attempt a HEAD request to confirm the endpoint responds without authentication.
    Affected if The upload endpoint responds without requiring authentication.

A user is affected if the Ninja Forms File Uploads plugin version is below 3.3.27, file uploads are enabled, and the upload endpoint is publicly accessible without authentication.

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 File Uploads plugin to version 3.3.27 or later to apply the full patch. If immediate update is not possible, consider disabling the file upload functionality or restricting upload endpoints at the web server level.

Recommended fix High confidence

3.3.27 or later

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the Ninja Forms plugin
  4. 4. Check the current version number
  5. 5. If the installed version is 3.3.26 or below, update the plugin to version 3.3.27 or later
  6. 6. Alternatively, download the latest version from the WordPress plugin repository or ninjaforms.com
  7. 7. Verify the update was successful by checking the plugin version after updating

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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