Security notice
Use the Ninja Forms File Uploads add-on? Someone without a login can delete or read files on your site. Update to 3.3.37 or later today.
The Ninja Forms File Uploads add-on for WordPress has CVE-2026-126537 in versions 3.3.36 and earlier. It lets someone without a login delete files on the server, or read files by sending them to a connected storage service such as Amazon S3, Dropbox or Google Drive. Deleting or reading the wrong files can lead to a site takeover. Wordfence rates it CVSS 9.1 (critical). Patchstack rates it 8.6. Patchstack marks it as known to be exploited. Wordfence published the record on November 11, 2026. The fix is version 3.3.37. This is a premium add-on, so check that your license is active and the update actually arrived. If you use this add-on, update to 3.3.37 or later today. If you cannot update, deactivate the add-on until you can. (Wordfence, Nov 11, Ninja Forms changelog, zeroday.news)
What happened
- The flaw. CVE-2026-126537 affects the Ninja Forms File Uploads add-on for WordPress in versions 3.3.36 and earlier. Someone without a login can delete files on the affected site, or read files by sending them to connected cloud storage (Amazon S3, Dropbox or Google Drive). That can lead to a site takeover. (Wordfence, GitHub Security Advisory GHSA-rfc5-f6j6-9jgj)
- Known to be exploited, per Patchstack. Patchstack marks this vulnerability as known to be exploited. That is Patchstack's own assessment. (zeroday.news)
- Severity. Wordfence rates it CVSS 9.1 (critical). Patchstack rates it 8.6. (Wordfence, Patchstack)
- The fix. The official changelog for version 3.3.37, dated November 2, 2026, lists security enhancements that harden handling of uploaded file data during form submission. Wordfence and the GitHub advisory identify 3.3.37 as the first fixed version. Update to 3.3.37 or later. (Ninja Forms changelog, Wordfence)
Who should worry
Any WordPress site running the Ninja Forms File Uploads add-on 3.3.36 or earlier. This is a paid add-on, not the free Ninja Forms plugin by itself. If you do not use this add-on, this notice does not apply to you.
What to do now
- Update the Ninja Forms File Uploads add-on to 3.3.37 or later today. Back up the site first. This is a premium add-on, so confirm your license is active, then in WordPress admin go to Plugins, Installed Plugins, and confirm the installed version even if automatic updates are enabled or your host manages updates. (Wordfence, Ninja Forms changelog)
- If the update has to wait, deactivate the add-on until you can install the fixed version. You can also take public forms that accept file uploads offline until the update is in place.
- Check for signs of tampering. Look for unexpected new administrator or user accounts, changed passwords, odd files or settings, and unfamiliar files in any connected Amazon S3, Dropbox or Google Drive folder used by the add-on. Updating closes the flaw; it does not undo access an attacker may already have gained.
- If you find signs of a break-in, change passwords, tell affected users, and ask your developer or host to investigate.
What to send your developer, agency or host
Please check whether our WordPress site runs the Ninja Forms File Uploads add-on (a premium add-on, not the free Ninja Forms plugin alone). CVE-2026-126537 affects versions 3.3.36 and earlier; unauthenticated attackers can delete or read files on the site, which can lead to site takeover, fixed in 3.3.37. Wordfence rates it 9.1. Patchstack marks it as known to be exploited. Please update us to 3.3.37 or later today, or deactivate the add-on until the update can be installed, then check for unexpected accounts, files or activity in connected cloud storage, and confirm the version you left us on. Sources: Wordfence, GitHub advisory GHSA-rfc5-f6j6-9jgj, Ninja Forms changelog, zeroday.news, NVD.
Common questions
Does this mean my site was hacked?
No. A vulnerable version is a reason to update and review the site, not proof of a break-in. Patchstack marks this flaw as known to be exploited, so do not wait.
Can EverThread tell me if I am affected?
No. EverThread does not test for this. We cannot see which WordPress plugins or add-ons your site runs or which versions they are on. A scan without a warning about this add-on does not mean your site is safe.
Which version should I install?
3.3.37 is the first version that fixes this flaw. Install 3.3.37 or later. You need an active Ninja Forms File Uploads license to receive the update. (Ninja Forms changelog)
Where can I follow updates?
Follow Wordfence, the GitHub advisory, the Ninja Forms File Uploads changelog, the NVD entry and zeroday.news. All current notices are on our notices page.
Security alerts by email
Hear about the next one first.
When a flaw puts websites at risk, we send one email: what happened, who it affects and what to do. It's free, whether or not you use EverThread.
Sources
- Wordfence: CVE-2026-126537, Ninja Forms File Uploads add-on versions 3.3.36 and earlier, patched in 3.3.37, CVSS 9.1 (critical), record published November 11, 2026. These details also appear in the GitHub advisory and in RescuePHP's write-up, which cites the Wordfence Intelligence record.
- GitHub Security Advisory GHSA-rfc5-f6j6-9jgj: CVE-2026-126537, published November 11, 2026 (10:31 AM ET), severity critical, CVSS 9.1 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H). The advisory text matches the Wordfence record: unauthenticated file deletion and file read via Amazon S3, Dropbox or Google Drive, fixed in 3.3.37.
- Ninja Forms File Uploads changelog: version 3.3.37, dated 2 November 2026, lists security enhancements that harden handling of uploaded file data during form submission. The changelog does not name this CVE. 3.3.37 was the newest version listed on that changelog when checked on November 15, 2026.
- zeroday.news: CVE-2026-126537. write-up of CVE-2026-126537, checked November 15, 2026.
- Patchstack: affected versions 3.3.36 and earlier, patched in 3.3.37, CVSS 8.6, marked as known to be exploited, dated 11 November 2026.
- RescuePHP: November 2026 write-up citing the Wordfence Intelligence record for CVE-2026-126537; affected through 3.3.36, fixed in 3.3.37, record published November 11, 2026.
- WordSec: CVE-2026-126537, affected versions 3.3.36 and earlier, patched in 3.3.37, CVSS 9.1, disclosed November 2026.
- NVD: CVE-2026-126537 record.