Skip to main content

Super Forms EUVDEUVD-2026-94737

| CVE-2026-17196 HIGH
Unrestricted Upload of File with Dangerous Type (CWE-434)
2026-10-08 Wordfence GHSA-r223-f6qv-r3gw
8.8
CVSS 3.1 · Vendor: Wordfence
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Register/authenticate as Subscriber
  2. Delivery
    Poison _super_elements meta via super_save_form AJAX
  3. Exploit
    Upload PHP payload via unauth super_upload_files
  4. Execution
    Request uploaded web shell
  5. Impact
    Remote code execution on server

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V5 - File Handling File type validation, storage isolation
MITRE ATT&CK

2 techniques across 2 tactics: Command and Control, Persistence

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires two chained conditions: (1) an authenticated Subscriber-level (or higher) account, used to invoke the super_save_form AJAX handler which lacks capability and nonce checks, to poison the _super_elements post meta with an attacker-chosen extensions string; and (2) a subsequent call to the super_upload_files endpoint, which performs the upload with NO authentication and applies the poisoned extensions string verbatim as its allowed MIME-type map, bypassing file-type validation. The key limiting factor is obtaining the initial Subscriber account - trivial on sites with open user registration, harder on sites that disable self-registration. Affects all versions up to and including 6.3.316; a non-default role restriction or disabled registration reduces, but does not eliminate, exposure.

Impact

This is a genuine high-priority issue, not a CVSS-inflated paper risk. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 8.8) is consistent with the description: network-reachable, low-complexity, and requiring only Subscriber-level privileges (PR:L) because the full chain depends on first poisoning the _super_elements post meta via super_save_form, which demands authentication. The CWE-434 unrestricted file upload culminates in remote code execution, justifying the H/H/H impact. No EPSS score, KEV listing, or public exploit was provided, so exploitation likelihood cannot be quantified from the inputs and must be treated as unknown rather than low. The practical risk driver is that Subscriber is the lowest meaningful authenticated role and is self-registerable on any WordPress site with open registration; the second stage (super_upload_files) requires no authentication at all. Net: a legitimately dangerous, easily reached RCE on affected installs, with the main uncertainty being real-world exploitation volume rather than technical validity.

Exploit ScenarioDerived

An attacker registers (or obtains) a Subscriber-level account on a WordPress site running Super Forms ≤6.3.316, then calls the super_save_form AJAX handler - which lacks capability and nonce checks - to write an attacker-controlled extensions string into the _super_elements post meta. They then invoke the unauthenticated super_upload_files endpoint, which trusts that poisoned MIME/extension map verbatim, to upload a PHP web shell and achieve remote code execution. No public exploit code was identified in the provided data, but the patch pull request (RensTillmann/super-forms #205) discloses the vulnerable code path.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.5% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 08, 2026

Unrestricted file upload in the Super Forms - Drag & Drop Form Builder WordPress plugin (all versions up to and including 6.3.316) lets an attacker write attacker-controlled file types to the server, which can be turned into remote code execution. Exploitation is a two-step chain: an authenticated Subscriber-level user poisons the _super_elements post meta with a crafted extensions string through the super_save_form AJAX handler, which lacks capability and nonce checks, and then the super_upload_files endpoint - which requires no authentication at all - applies that string verbatim as its allowed MIME-type map and accepts an executable file. Rated CVSS 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), with the practical barrier being acquisition of a low-privileged account, which is trivial on sites with open registration; no public exploit identified at time of analysis.

RemediationAI

Apply the upstream fix tracked in GitHub pull request https://github.com/RensTillmann/super-forms/pull/205 - note this is an upstream fix available (PR/commit); a released patched version number is not independently confirmed in the supplied data, so verify the fixed build on the vendor page before relying on a specific version. Where the plugin cannot be updated immediately, the highest-value compensating control is to remove the ability to obtain a Subscriber-level account: disable open user registration and review existing low-privileged accounts, understanding this only raises the bar since any existing contributor-level account still satisfies the prerequisite. Additionally, block or disable the super_save_form AJAX action at the web-server/WAF layer and restrict or block requests to the super_upload_files endpoint (for example, requiring an authenticated session and denying direct POSTs to admin-ajax.php action=super_upload_files) - the trade-off is that these endpoints are core to the plugin's form-building workflow, so blocking them may break legitimate form editing and front-end uploads. Deactivating the plugin entirely removes the exposure if it is not business critical, and a WAF rule rejecting uploaded files whose extensions do not match a hardened, hard-coded allow-list (php, phtml, phar, and similar) provides a backstop but should be treated as defense in depth rather than a fix, because the underlying trust of attacker-controlled meta persists.

Affected VersionsENISA

Super Forms – Drag & Drop Form Builder 0 ≤6.3.316

Affected Packages

euvd super_forms_drag_drop_form_builder no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The root cause is CWE-434 (Unrestricted Upload of File with Dangerous Type), but the interesting part is that validation is not merely absent - it is replaced by attacker-supplied data. The plugin's upload_files function reads an extensions string out of the _super_elements post meta and uses it verbatim as the allow-list/MIME-type map for uploaded files. That meta value is writable through the super_save_form AJAX handler, which performs neither a capability check nor a nonce check, so any authenticated user at Subscriber level or above can set it. A separate endpoint, super_upload_files, then performs the actual upload with no authentication requirement whatsoever and trusts the poisoned meta. The result is a confused-deputy design in which the security policy for file uploads is stored in user-modifiable content rather than hard-coded or validated. Per the supplied CPE identifier (cpe:2.3:a:webrehab:super_forms_-_drag_&_drop_form_builder), the affected component is the WordPress plugin distributed by webrehab, and the flaw spans every release through 6.3.316.

Know when Super Forms Drag Drop Form Builder gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Wordfence) PRIMARY 8.8 HIGH
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 8.8 HIGH

PR:L because the end-to-end chain requires a Subscriber account to poison the post meta first; network/low-complexity with no user interaction, and RCE yields full C/I/A impact.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (Wordfence).

CVSS VectorVendor: Wordfence

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

The Super Forms - Drag & Drop Form Builder plugin for WordPress is vulnerable to Unrestricted File Type Upload in all versions up to, and including, 6.3.316 via the upload_files function. This is due to missing file type validation in the upload_files function, which reads and applies an attacker-controlled extensions string from _super_elements post meta verbatim as the allowed MIME type map. This makes it possible for authenticated attackers, with Subscriber-level access and above, to upload files that may be executable, which makes remote code execution possible. The attack requires a preceding step: poisoning the _super_elements post meta via the super_save_form AJAX handler, which lacks a capability and nonce check but requires the attacker to be authenticated as at minimum a Subscriber-level user; the subsequent file upload via super_upload_files requires no authentication at all.

Executive ViewAI

Why It Matters

The Super Forms - Drag & Drop Form Builder WordPress plugin (all versions up to and including 6.3.316) contains a high-severity unrestricted file upload vulnerability that can lead to remote code execution. Affected organizations running this plugin face potential full site compromise, data theft, and service disruption, especially if open registration allows attackers to easily obtain a low-privileged Subscriber account; exploitation requires authenticated low-privileged access (PR:L). No public exploit identified at time of analysis, and no vendor-released patch identified at time of analysis, so leadership should prioritize immediate mitigation and monitoring.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include disabling the Super Forms plugin (all versions up to and including 6.3.316) on all WordPress sites, restricting access to the super_upload_files endpoint via WAF rules, disabling open user registration to prevent Subscriber-level account creation, auditing existing user accounts for unauthorized Subscriber-level users, and disabling PHP execution in file upload directories.

Threat Intelligence Overview

EPSS Score
0.5%
Top 57% exploitable
Prevalence
Medium
popular commercial WordPress form-builder plugin, moderate but not universal footprint
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.5%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

45
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Malicious file upload attacks exploit insufficient validation when web applications accept user-provided files.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy