Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2026-0740: Unauthenticated Arbitrary File Upload in Ninja Forms File Uploads

Published Apr 7, 2026 · Updated 10 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS9.8Critical · v3.1
EPSS62.9%99th percentile
CISA KEVNoNot listed
In the wildReported15 exploitation records in Mallory
IdentifiersCVE-2026-0740CWE-434 · Unrestricted Upload of File with…

CVE-2026-0740 is an unauthenticated arbitrary file upload vulnerability in the Ninja Forms File Uploads add-on for WordPress through version 3.3.26. The NF_FU_AJAX_Controllers_Uploads::handle_upload() function delegates processing to _process(), which validates the source filename but insufficiently validates the attacker-controlled destination filename before moving the uploaded file. Attackers can specify dangerous executable extensions and use path traversal to place malicious files outside the intended upload directory. Uploaded PHP code can enable remote code execution when accessed through the web server. Versions 3.3.25 and 3.3.26 contain incomplete fixes; version 3.3.27 fully addresses the vulnerability. The vulnerability is actively exploited.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Unauthenticated attackers can write arbitrary uploaded files to server locations permitted by the web application’s filesystem privileges. If an uploaded executable file is web-accessible and processed by the server, exploitation enables arbitrary code execution under the web application’s security context. This can lead to webshell deployment, persistent access, website takeover, credential and database theft, content modification, malware distribution, and service disruption. Further network compromise depends on the compromised server’s privileges and connectivity.

Mitigation

If you can’t patch tonight, do this now.

Until the update can be deployed, disable the vulnerable File Uploads add-on or block access to its upload functionality. Apply available CVE-specific WAF or IPS protections, including Wordfence’s firewall rule, as a temporary compensating control. Restrict filesystem write permissions and prevent script execution in upload directories where feasible; upload-directory restrictions alone may be insufficient because destination filenames support path traversal. Monitor unexpected executable file creation and suspicious web server child processes, and restrict connectivity between public web servers and internal networks.

Remediation

Patch, then assume compromise.

Upgrade the Ninja Forms File Uploads add-on to version 3.3.27 or later. Versions 3.3.25 and 3.3.26 are not sufficient. The complete fix normalizes and sanitizes destination filenames, removes directory components, and rejects prohibited executable extensions. Because exploitation is ongoing, verify website filesystem integrity and review upload activity and web server logs after updating. If compromise is identified, isolate the server, preserve evidence, remove malicious files and persistence, rotate exposed credentials, and restore from a known-good backup where necessary. Updating alone does not remove an existing compromise.

Public exploits

Exploits

6 exploits validated by Mallory's analysis. Hidden: 3 rejected by Mallory's analysis as not a working exploit; 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
CVE-2026-0740This repository is a small standalone Python exploit for CVE-2026-0740 affecting the WordPress Ninja Forms - File Uploads extension up to version 3.3.26. The repository contains one primary code file (CVE-2026-0740.py), a README with exploitation guidance and examples, and a minimal requirements.txt listing httpx and socksio. The exploit is not part of a larger offensive framework. Its workflow is straightforward: it accepts a target URL, a local file to upload, an optional destination path/filename, optional proxy settings, custom headers, and timeout values. It then sends a POST request to the WordPress AJAX endpoint /wp-admin/admin-ajax.php with action=nf_fu_get_new_nonce and a randomly generated field_id to obtain a valid upload nonce without authentication. After receiving the nonce, it performs a second multipart POST to the same endpoint with action=nf_fu_upload, attaching the attacker-controlled file while masquerading it as image.jpg and abusing the image_jpg POST parameter to control the final destination filename/path. The main exploit capability is unauthenticated arbitrary file upload. Because the destination filename is attacker-controlled, the exploit can be used to write files with dangerous extensions or traverse directories, depending on the vulnerable plugin version. The README explicitly documents that path traversal works on <= 3.3.24 and that later vulnerable versions still permit dangerous extension manipulation until 3.3.27 fully fixes the issue. The exploit itself does not generate a payload; instead, it uploads any user-supplied file. The README demonstrates using a PHP webshell payload to achieve remote command execution via a URL such as /wp-content/uploads/ninja-forms/ws.php?cmd=id. Notable fingerprintable targets and indicators include the WordPress AJAX endpoint /wp-admin/admin-ajax.php, the AJAX actions nf_fu_get_new_nonce and nf_fu_upload, the abused POST parameter image_jpg, and the upload path /wp-content/uploads/ninja-forms/tmp/. The script also uses a default traversal destination of ../../../, which is a strong indicator of intended arbitrary path placement. Overall, this is a real, functional exploit PoC with operational capability: it automates nonce retrieval and malicious upload, but leaves payload selection to the operator.whattheslime · Disclosed Apr 7, 2026 · python · markdown · web · networkOperationalCVE-2026-0740Repository contains a README and one Python exploit script, shadow.py. The script is a mass-exploitation tool for CVE-2026-0740 affecting the WordPress Ninja Forms - File Uploads plugin <= 3.3.26. Its workflow is: read target URLs from list.txt, POST to /wp-admin/admin-ajax.php with action=nf_fu_get_new_nonce using hardcoded form_id=7 and field_id=7, parse the returned nonce, then POST again to the same endpoint with action=nf_fu_upload and a multipart file upload. The uploaded content is a PHP web uploader disguised as doc.pdf with MIME type application/pdf, while the POST parameter doc_pdf requests server-side renaming to shadow.php. On success, the script constructs the shell URL under /wp-content/uploads/ninja-forms/tmp/shadow.php, prints it, and appends it to shell.txt. The exploit is operational rather than a simple PoC because it includes a working payload and supports batch targeting, but payload customization is minimal and hardcoded. The main capability is unauthenticated arbitrary file upload leading to remote code execution via a web-accessible PHP shell.xShadow-Here · Disclosed Apr 8, 2026 · python · markdown · webOperationalCVE-2026-0740This repository contains a standalone Python exploit and a companion Nuclei template for CVE-2026-0740, an unauthenticated arbitrary file upload vulnerability in the WordPress Ninja Forms File Uploads plugin up to version 3.3.26. The repository structure is small and focused: one Python exploit script (CVE-2026-0740.py), one YAML detection/verification template (CVE-2026-0740.yaml), plus README and license files. The main exploit capability is unauthenticated file upload via the plugin’s WordPress AJAX interface. Based on the README and YAML flow, exploitation works by first requesting a nonce from /wp-admin/admin-ajax.php using the nf_fu_get_new_nonce action, then submitting a multipart upload using nf_fu_upload. The README indicates support for path traversal through a destination parameter, allowing more controlled placement of the uploaded file. The operator provides the payload file locally, such as a PHP web shell, and the script attempts to confirm the resulting accessible URL. This makes the exploit operational rather than a simple proof of concept. The Python script is a custom exploit tool, not tied to a major exploitation framework. It uses httpx and httpx-socks, supports custom headers, configurable timeout, optional SOCKS5 proxying, optional SSL verification, colored logging, and command-line arguments for target URL, local file, and destination path. The visible code shows client setup, proxy handling, and invocation of an exploit() routine; the README confirms the intended workflow and options. The YAML file is a Nuclei-style template, but the repository as a whole is not primarily a framework module; it serves as both exploit and detection/verification material. Fingerprintable target endpoints include the WordPress AJAX endpoint /wp-admin/admin-ajax.php, the upload verification path under /wp-content/uploads/ninja-forms/tmp/, and the AJAX action names nf_fu_get_new_nonce and nf_fu_upload. The exploit targets web-accessible WordPress installations running the vulnerable plugin. Successful exploitation can result in arbitrary file placement and possible remote code execution if the uploaded file is executable by the server.0xgh057r3c0n · Disclosed Apr 17, 2026 · python · yaml · webOperationalCVE-2026-0740Repository is a small standalone Python exploit tool consisting of three files: README.md, a large target list (list.txt), and the main script (ninja.py). The script is not part of a known exploit framework. Its purpose is mass exploitation of WordPress sites using Ninja Forms upload-related AJAX actions. For each target URL from list.txt, it constructs the endpoint /wp-admin/admin-ajax.php, requests a nonce using action=nf_fu_get_new_nonce with hardcoded FORM_ID=7 and FIELD_ID=7, then attempts a multipart upload using action=nf_fu_upload. The uploaded content is a PHP web shell/uploader stored under the server-side name murrez.php while the multipart filename is disguised as doc.pdf with MIME type application/pdf. If the JSON response indicates success and references the expected tmp_name, the script assumes the shell is reachable at /wp-content/uploads/ninja-forms/tmp/murrez.php and appends that URL to shell.txt. The code disables TLS verification, suppresses urllib3 warnings, uses a generic Mozilla user-agent, and includes basic exception handling and progress output. This is an operational mass-upload exploit with a hardcoded payload rather than a detection script.murrez · Disclosed Apr 25, 2026 · python · markdown · webOperationalCVE-2026-0740Single-file Python exploit targeting a WordPress Ninja Forms upload vulnerability labeled CVE-2026-0740. The script is an interactive, multithreaded exploitation tool rather than a mere detector. It accepts either a file of targets or manual target input, accepts a local payload file, and then concurrently attacks each target. For each host, it normalizes the URL to try HTTPS then HTTP, requests a nonce from /wp-admin/admin-ajax.php using the nf_fu_get_new_nonce action, and then submits a multipart upload using nf_fu_upload. The exploit abuses the image_jpg parameter to set a traversal-based destination path using the hardcoded prefix ../../../../ plus the supplied filename. If the server response indicates the temporary name matches the traversal path, the script constructs a public URL under /wp-content/uploads/ninja-forms/tmp/ and fetches it to validate success. Validation is tailored to a specific uploaded web shell or file manager payload by checking for 'File Manager' markers in the HTTP response body. Successful URLs are appended to vuln_ninja.txt. Repository structure is minimal: one Python script containing constants, logging helpers, target loading, URL normalization, upload/validation logic, threaded worker orchestration, and the CLI main entry point.zycoder0day · Disclosed May 11, 2026 · python · web · networkOperationalCVE-2026-0740-massRepository contains a single Python exploit script and a README. The main file, CVE-2026-0740.py, is a standalone mass-target exploit for CVE-2026-0740 affecting the WordPress Ninja Forms - File Uploads plugin <= 3.3.26. It is not part of a larger exploit framework. The script accepts either a single target or a file of targets, supports concurrent exploitation with a thread pool, optional proxying, custom headers, configurable timeout, and writes successful shell URLs to an output file. Based on the visible code and README, the exploit chain is: normalize target URL, request an unauthenticated upload nonce from the WordPress AJAX endpoint, abuse the vulnerable upload handler to submit an attacker-supplied file, override the destination filename/path using traversal (default ../../../), and derive/log the resulting shell URL when upload succeeds. The intended outcome is arbitrary file upload leading to remote code execution when a server-executable payload such as a PHP/PHT webshell is used. Fingerprintable targets and artifacts include /wp-admin/admin-ajax.php, the AJAX actions nf_fu_get_new_nonce and nf_fu_upload, and WordPress content/upload paths such as wp-content/uploads/ninja-forms/tmp/, wp-content/uploads/ninja-forms/, and wp-content/. The README also documents IOC locations, mitigation guidance, and example shell verification requests. Overall, this is an operational exploit tool rather than a detector: it automates exploitation at scale and supports attacker-provided payloads, but payload customization is manual rather than framework-driven.ExDev994 · Disclosed Jul 11, 2026 · python · markdown · web · networkOperational
FAQ

Frequently asked questions

Is CVE-2026-0740 exploited in the wild?
Yes. As of Nov 8, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2026-0740?
Yes. Mallory tracks 6 public exploits or proofs of concept for CVE-2026-0740, the earliest disclosed Apr 7, 2026.
Is there a patch for CVE-2026-0740?
Upgrade the Ninja Forms File Uploads add-on to version 3.3.27 or later. Versions 3.3.25 and 3.3.26 are not sufficient.
How severe is CVE-2026-0740?
CVE-2026-0740 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 62.9% (99th percentile) as of Nov 8, 2026.
Activity feed

Recent activity

49 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+14 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malware12Malware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity31Community discussion across Reddit, Mastodon, and other social sources.