On this page (7 sections)
A critical vulnerability, tracked as CVE-2026-126537, affects the Ninja Forms - File Uploads add-on for WordPress. According to the NVD record, an unauthenticated attacker can delete arbitrary files on the web server, and the record says this may make remote code execution possible.
If your site uses Ninja Forms with the paid File Uploads extension, check your version today. The research available at publication does not name a fixed version, so the first step is to find out what you are running and what the vendor now offers.
What happened
The NVD entry, published on 2026-11-11, describes an arbitrary file deletion flaw in the File Uploads add-on. The record also mentions arbitrary file read via S3, Dropbox and Google Drive exfiltration, because the attacker-supplied file path ends up in the add-on's background upload queue, which the S3 upload code uses as the source file.
The most serious consequence the record describes is the deletion of wp-config.php. It states that deleting this file forces WordPress into its setup screen, enabling full site takeover. It also says that deleting arbitrary files may make remote code execution possible.
Technical details in plain terms
The weakness class is path traversal (CWE-22): the plugin trusts a file location supplied by the visitor and then acts on it without checking that it sits inside the intended upload folder. According to the record, two pieces of plugin code combine to cause this.
- The upload field handler returns early when a public submission carries a non-empty saveProgress value, which leaves the client-supplied file list untouched instead of replacing it with trusted data.
- The external service handler only reloads the authoritative file path when the client sends an upload_id. If that value is left out, the attacker's file path survives into the background upload queue.
- That path is then used both when sending a file to S3 and when the plugin deletes a local file afterwards, with no canonicalization or upload-directory containment check.
- The plugin already contains a helper that checks whether a path is inside the upload directory, but according to the record it is applied only on admin paths.
In short, a public submission can make the server delete a file the visitor chose, and the record says the same path can feed file read through the external storage integrations. No login is needed, which is why the score is high. We deliberately do not describe request details beyond this, since they are not needed to defend a site.
Who is affected
Sites running the File Uploads add-on at version 3.3.36 or earlier are in scope. The free Ninja Forms core plugin is not named in the record; the flaw is in the add-on.
The record does not spell out which site configurations are required to reach the vulnerable code. It does not say whether a public form with a file upload field must exist, or whether S3, Dropbox or Google Drive must be connected for the deletion to work. The file read and exfiltration part is described in terms of those external services, so sites using them may carry extra risk. Until the vendor clarifies, treat any site with the add-on installed at 3.3.36 or earlier as exposed.
How to check your exposure
First confirm whether the add-on is installed and which version it is. This WP-CLI command lists installed plugins with their status and version; run it from the WordPress root. Look for an entry for Ninja Forms File Uploads and compare its version with 3.3.36.
wp plugin list --fields=name,status,version,updateYou can also open Plugins in the WordPress admin and read the version under the add-on's name. Next, confirm that your core files are intact. This command checks WordPress core files against the official checksums; it does not cover wp-config.php, so also confirm that file exists.
wp core verify-checksumsls -l wp-config.phpA missing wp-config.php, or a site suddenly showing the WordPress setup screen, is a strong sign of trouble and should be treated as an incident.
What to do now
- Find out whether the File Uploads add-on is installed and note its version.
- Check the vendor's File Uploads extension page and your account for a release newer than 3.3.36, then update as soon as one is available.
- If no fixed release is available, deactivate the add-on until one is. Removing the upload field from public forms may also reduce exposure, but the record does not confirm that this is enough.
- Take a full backup of files and database now, and store it off the server.
- If the add-on is linked to S3, Dropbox or Google Drive, review recent activity there and consider rotating the access keys or tokens the plugin uses.
- Check that wp-config.php and other key files are present and unchanged.
- As general hardening, review file and directory permissions so the web server user can modify only what it needs to.
- Review web server logs for the setup screen being requested unexpectedly and for unusual form submissions.
- If you find missing files or signs of takeover, follow a structured recovery process and rotate all credentials and secret keys.
Detection and monitoring afterwards
Arbitrary file deletion often leaves little trace except the missing file and its fallout, so watch for the symptoms. Set up uptime monitoring that alerts you if your home page suddenly returns an installation screen or an error, and keep file integrity checks running on a schedule. Webforta Monitor covers uptime, certificate, DNS and header-change monitoring, which helps you notice a site that has gone down or changed unexpectedly, although it does not detect this flaw itself.
This log search looks through an Nginx access log for requests to the WordPress setup scripts, which you would normally not expect on a live site. Adjust the log path for your server (Apache logs are often under /var/log/apache2/ or /var/log/httpd/); any hits you did not cause deserve investigation.
grep -E "wp-admin/(setup-config|install)\.php" /var/log/nginx/access.logFor wider guidance on keeping plugins under control, see our guide on checking whether a WordPress plugin is vulnerable and the WordPress security checklist. If you suspect compromise, what to do when a website is hacked walks through recovery.
What we do not know yet
- No patched version is named in the sources we reviewed.
- No exploitation in the wild is reported, but absence of reports is not proof of safety for a flaw that needs no login.
- The record does not state which configurations (public upload field, external storage connected) are required to trigger the flaw.
- The CVSS score of 9.1 is listed in the NVD record; the source material does not break out the individual vector metrics.
- Only one independent publisher covers the issue so far, so details may be refined as the vendor and other researchers respond.
We will treat any vendor statement as the authority on fixed versions once it is available. Until then, the safest assumption is that every release up to and including 3.3.36 is vulnerable.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
