Checked as of 11 November 2026. Three WordPress form plugins received public advisories in the same week, and each one turns on how the plugin handles a file: deleting it, writing it, or emailing it. This roundup is for site owners and whoever they hand the work to. It covers what each issue needs before it matters, which response is justified, and how to confirm the job was done.
Three issues side by side
| Topic | CVE | Affected | Fix status | Preconditions | Main risk |
|---|---|---|---|---|---|
| Ninja Forms File Uploads add-on | CVE-2026-126537 | 3.3.36 and earlier | 3.3.37, vendor release 2 November 2026 | Paid add-on active, public form using the background upload path, storage configuration needs assessment | Arbitrary file deletion, possible read through configured S3, Dropbox or Google Drive |
| ARForms | CVE-2026-111190 | 7.2.4 and earlier | 7.3, vendor release dated 7 November 2026 | Published public form with a File field | PHP file written to a public directory; execution depends on server configuration |
| Everest Forms | CVE-2026-115483 | 3.6.3 and earlier | Not established; vendor 3.6.4 dated 5 November 2026 changed signature handling | Pro add-on, Attach Files on an email notification, any field whose meta key contains signature_, recipient taken from submitter input | Arbitrary local file read by email, including wp-config.php |
Advisory dates are disclosure dates, not patch dates. Wordfence published the Ninja Forms entry on 11 November and the other two on 10 November 2026. The public CNA record for the Everest Forms CVE was available during this check and corroborates the Wordfence description. The Ninja Forms and ARForms CNA endpoints returned no record, so those two rely on Wordfence and vendor material only. No reviewed source establishes active exploitation of any of the three.
Ninja Forms File Uploads add-on (CVE-2026-126537)
Applicability. Only the paid File Uploads add-on is affected, not Ninja Forms core. An unauthenticated public submission can feed an untrusted local file path into background upload handling. Wordfence reports arbitrary deletion and potential file read through configured external storage, but the exact storage and configuration prerequisites are not fully qualified. Do not assume every installation, or cloud storage alone, is exploitable.
Recommended action. Patch to 3.3.37 or later. The vendor shipped that version on 2 November 2026 with hardened submission data, uploads bound to their form and field, and protected external links. Deleting a configuration file may enable takeover under additional conditions, so check for missing files after updating; an update cannot restore what was deleted. If you cannot patch, assess disabling the add-on or the forms that use it. The reviewed sources do not establish a guaranteed workaround.
Sources: Wordfence advisory, vendor extension page. Record: /security/ninja-forms-uploads-background-file-deletion/.
ARForms (CVE-2026-111190)
Applicability. ARForms 7.2.4 or earlier with a published, publicly reachable form that contains a File field. A crafted filename or header bypasses the upload checks and lands a PHP file in a public directory. Whether that becomes code execution depends on the server’s execution configuration. ARForms Lite is a different product and is not covered by this range.
Recommended action. Patch to 7.3 or later. The CVE, affected range and fixed floor come from Wordfence. The vendor changelog dates 7.3 to 7 November 2026 and describes only minor fixes, which corroborates the release and date but not this specific CVE. Remove public File fields you do not need. Moving a visible form to another page is not a proven mitigation for the upload endpoint. Preserve evidence of any unexplained file before it is isolated or removed.
Sources: Wordfence advisory, vendor changelog. Record: /security/arforms-public-file-upload/.
Everest Forms (CVE-2026-115483)
Applicability. The narrowest preconditions of the three, and the least settled fix. You need the Pro add-on, an email notification with Attach Files enabled, any field whose meta key contains the text signature_, and a recipient routed from submitter input. The field does not have to be a signature-type field; the CNA record gives a plain text field labelled “Signature” as the example. When all four hold, an unauthenticated submission can attach an arbitrary local file, such as wp-config.php, and mail it to an attacker-supplied address. No standalone code execution is claimed.
Recommended action. Contain, then confirm. Wordfence lists no known patch. The vendor’s 3.6.4 release, dated 5 November 2026, describes improved handling of signature files in email attachments. A source comparison shows 3.6.3 only checked that a path existed, while 3.6.4 resolves the real path and requires the expected per-form signature directory. That is meaningful hardening, not confirmed clearance of the CVE, and no minimum fixed version is declared here. The CNA record marks versions above 3.6.3 as unaffected by default, which is a record convention rather than an explicit confirmation that 3.6.4 fixes the issue. Ask your provider or the vendor to confirm the complete fix and the affected workflow. Meanwhile, assess disabling the attachment workflow, the Pro-dependent form, or the plugin, and have your provider confirm the affected processing is actually disabled. Review recipient settings and access logs. If a leak is evident, have your provider handle credential rotation and incident response rather than improvising.
Sources: Wordfence advisory, CNA record, vendor readme, 3.6.3 upload class, 3.6.4 upload class. Record: /security/everest-forms-signature-email-file-read/.
A worked handoff
Suppose an owner runs a quote form on ARForms 7.2.1 with a File field and a separate contract form on Everest Forms 3.6.3 with the Pro add-on and Attach Files switched on. They send a freelancer this brief:
- Confirm a restorable backup exists and record its timestamp. The rules in backup strategy apply.
- Update ARForms to 7.3 or later. Submit a harmless test with your own file, and confirm storage and notification email still work.
- For Everest Forms, do not treat 3.6.4 as a fix. Turn off Attach Files on the contract form notification and record the settings before and after. Submit a harmless test to confirm the form still works and no attachment arrives; this checks normal function only, not whether the attacker-controlled path is closed. Keep the form offline if the business can wait.
- List any files in upload or public directories that nobody can explain. Preserve a copy and the related logs as evidence, then hand them to the hosting provider for isolation, quarantine or cleanup. Do not leave a possibly executable file reachable from the web just so it can be reviewed later.
- Report plugin names, exact before and after versions, the settings changed, and the test results with their limits.
Acceptance checks
- Patch check (Ninja Forms File Uploads, ARForms): the version shown in the admin is at or above the fixed floor, a real test submission succeeded, and the test produced no storage or email error. Updating is not evidence that nothing happened earlier.
- Containment check (Everest Forms): the provider confirms the affected processing is disabled and the settings and the benign functional test are recorded with their limits, or the plugin is deactivated. A benign test that produces no attachment confirms normal function, not that the path cannot be bypassed, and no exploit test is needed. If the provider cannot verify that processing stopped, assess deactivating the plugin. Containment stays in place until the provider or vendor confirms the complete fix.
- Incident response check (any of the three): unexplained files, missing files, unusual recipients, or signs of secret exposure. Stop treating it as maintenance, preserve logs, and follow what to do when your website is hacked. Credential rotation after a suspected wp-config.php leak belongs with your provider.
None of this guarantees protection. It gives an owner a checkable standard for the work.