Critical PHP2Shell: two unauthenticated RCE flaws in PHP itself. Fixes shipped on 21 Oct 2026. Check if you are affected →
← All news

Ninja Forms File Uploads 3.3.37 Fixes Unauthenticated File Deletion That Can Wipe wp-config.php (CVE-2026-126537)

The Ninja Forms File Uploads add-on through 3.3.36 let anonymous visitors delete arbitrary server files, and push them to S3, Dropbox or Google Drive, through a public form. Update to 3.3.37.

A newly published vulnerability in the Ninja Forms – File Uploads add-on for WordPress lets unauthenticated visitors delete arbitrary files on the server. It is tracked as CVE-2026-126537, affects versions up to and including 3.3.36, and is fixed in 3.3.37. The record was published by Wordfence Intelligence on November 11, 2026.

What goes wrong

According to the Wordfence record, the bug sits across two pieces of the add-on:

  • NF_FU_Fields_Upload::process() (includes/fields/upload.php) returns early whenever a public submission carries a non-empty extra.saveProgress value. When it does, the client-supplied files[] data is left untouched.
  • NF_FU_External_Abstracts_Service::process_upload() only reloads the trusted, server-side file path when the client sends an upload_id. If the attacker simply omits it, their own data[file_path] survives into the background upload queue.

That attacker-controlled path is then used in two places: as the SourceFile for an upload to S3, and in the unlink() call that is supposed to clean up the local copy. Neither applies canonicalization or checks that the path stays inside the uploads directory. The plugin has an is_path_within_upload_dir() helper, but it is only used on admin paths.

Why it matters

  • File deletion without a login. Any site with a public form containing a file upload field is exposed.
  • A route to takeover. Deleting wp-config.php sends WordPress back to its installation screen, where an attacker can connect the site to a database they control.
  • File read, too. On sites that send uploads to S3, Dropbox or Google Drive, the same path can push sensitive server files, such as configuration files, out to that external storage.

What to do

  1. Update Ninja Forms – File Uploads to 3.3.37 or later. This is a premium add-on, so check that your licence is active and the update actually arrived.
  2. If you can't update right away, deactivate the add-on or unpublish forms that contain upload fields. A WAF rule blocking submissions that carry saveProgress together with a file_path is a reasonable stopgap.
  3. After updating, confirm wp-config.php is still present and the site doesn't show the installer, look for unfamiliar administrator accounts, and compare plugin, theme and config files against a backup.
  4. If you use cloud storage integrations, check the connected bucket or folder for files that don't belong to any form submission. If you find any, rotate database passwords and WordPress salts.

The bigger picture

This is another case of a public form handler trusting a path the client sent back. Background or deferred processing paths are easy to miss in reviews because the dangerous operation (unlink(), an upload to S3) happens far away from the request that supplied the data.

If your WordPress site runs older premium add-ons that you can't easily update, or you're not sure whether a file was touched, RescuePHP can help audit the install, patch or back-port fixes, and harden form upload handling.


Source: Wordfence Intelligence record for CVE-2026-126537. Vulnerability information Copyright 2012-2026 Defiant Inc., used under Defiant's vulnerability data license.