Skip to main content

Super Forms CVE-2026-17609

| EUVDEUVD-2026-94736 CRITICAL
Unrestricted Upload of File with Dangerous Type (CWE-434)
2026-10-08 Wordfence GHSA-pchj-gc42-gqq7
9.1
CVSS 3.1 · Vendor: Wordfence
View

Attack ChainAIDerived

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

  1. Access
    Identify site with delete-after-submit enabled
  2. Delivery
    Send crafted submit_form request with malicious JSON paths
  3. Exploit
    Bypass ABSPATH guard via dirname() trailing-slash strip
  4. Execution
    Recursively delete arbitrary server directory
  5. Impact
    Destroy WordPress root and take site offline

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 that an administrator has enabled the 'Delete files from server after form submissions' setting - without this feature active, the vulnerable deletion code path is not reached. Given that prerequisite, exploitation is remote and unauthenticated (PR:N) with no user interaction, triggered by sending crafted JSON field declarations to the submit_form function that evade schema validation; the ineffective ABSPATH guard is defeated because dirname() strips the trailing slash. The primary limiting factor is the non-default configuration dependency (the deletion feature must be on); affected versions are all releases up to and including 6.3.316.

Impact

This is a high-priority issue that warrants prompt patching, but its real-world risk is gated by a configuration precondition rather than being universally exploitable. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) describes a remotely reachable, unauthenticated, low-complexity flaw with high integrity and availability impact (C:N/I:H/A:H, base 9.1) - recursive deletion of arbitrary directories including the WordPress root can fully destroy a site, which justifies the critical scoring. Confirming signals: the vulnerability was reported by Wordfence (a credible threat-intel source) and a fix exists (GitHub PR #205). Conflicting/limiting signals: exploitation is NOT possible against a default install - it requires an administrator to have enabled the 'Delete files from server after form submissions' setting, which is a target-specific, non-attacker-controlled condition the raw CVSS AC:L does not reflect (CVSS 4.0's AT:P captures this better). No EPSS score, KEV listing, or public exploit code was provided in the input, so current active-exploitation evidence is absent. Net: a genuinely dangerous flaw in deployments that enabled the deletion feature, but the 9.1 likely overstates risk for the subset of installs running default configuration.

Exploit ScenarioDerived

An unauthenticated attacker identifies a WordPress site running Super Forms with the 'Delete files from server after form submissions' feature enabled, then submits a crafted form request to the submit_form endpoint containing malicious JSON field declarations whose paths are not validated against the real form schema. Because the ABSPATH guard is bypassed by dirname() stripping the trailing slash, the plugin recursively deletes an attacker-chosen directory - up to and including the WordPress root - causing total site destruction. No public exploit code is identified at time of analysis, though a patch PR publicly documents the vulnerable logic.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet 0.3% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Oct 08, 2026

Unauthenticated attackers can recursively delete arbitrary directories - including the WordPress installation root - on sites running the Super Forms - Drag & Drop Form Builder plugin for WordPress in all versions up to and including 6.3.316. The flaw is reachable by sending crafted JSON field declarations to the submit_form function that are not validated against the actual form schema, and it is compounded by an ABSPATH guard that dirname() trivially defeats by stripping the trailing slash. Exploitation is remote, unauthenticated (PR:N) and requires no user interaction, but is gated by a configuration prerequisite: an administrator must have enabled the documented 'Delete files from server after form submissions' setting, without which the vulnerable deletion code path is never reached; no public exploit identified at time of analysis.

RemediationAI

Upstream fix available (PR/commit); released patched version not independently confirmed - the referenced change at https://github.com/RensTillmann/super-forms/pull/205 addresses the vulnerable code path, so administrators should upgrade Super Forms to the first release published above 6.3.316 as soon as it appears in the WordPress.org plugin channel or the vendor repository, and verify the fix against the Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/f21577b4-b7c6-4b39-b2b7-66a75c5f56fb?source=cve. Because the vulnerability requires the 'Delete files from server after form submissions' setting to be enabled, the most immediate compensating control is to disable that option; the trade-off is that uploaded submission files will no longer be cleaned up automatically and will accumulate on the server, requiring manual or scheduled cleanup, and any dependent workflow that relies on post-submission deletion will break. Where the deletion feature cannot be turned off, deactivating the plugin entirely until a patched build is available removes the attack surface at the cost of losing all form functionality on the site. Site owners should also ensure the web server user has the minimum filesystem permissions needed, so that any residual path-traversal-style deletion is confined to non-critical directories rather than the WordPress root.

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 vulnerability sits in the form-submission handling of the Super Forms WordPress plugin, which is tracked by CPE as cpe:2.3:a:webrehab:super_forms_-_drag_&_drop_form_builder:* (vendor webrehab, upstream repository RensTillmann/super-forms). The core defect is a trust-boundary failure: JSON field declarations supplied by the request submitter are processed without being validated against the form's actual schema, so attacker-controlled metadata can steer the plugin's server-side file handling toward arbitrary paths. The plugin's protection against direct file access is a classic ABSPATH check, but because it is evaluated against a path built via dirname(), an attacker can append or omit the trailing path separator so that dirname() strips the slash and the guard no longer matches - effectively neutralizing the check. This is what elevates the issue from a form-handling bug into arbitrary recursive directory deletion with high integrity and availability impact (I:H/A:H) and no confidentiality impact (C:N), consistent with the assessed CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H score of 9.1. The CWE-434 (Unrestricted Upload of File with Dangerous Type) classification reflects the broader pattern of unvalidated file-related input being accepted from an untrusted source; the practical consequence here is destructive deletion rather than code execution. The single practical gate is the optional-but-commonly-enabled 'Delete files from server after form submissions' feature, which must be active for the deletion routine to run at all.

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 9.1 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
vuln.today AI 9.1 CRITICAL

Remote unauthenticated (AV:N/PR:N/UI:N); no confidentiality impact (C:N); arbitrary recursive directory deletion yields high integrity and availability loss (I:H/A:H); the config precondition is environmental, not attacker privilege.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
4.0 AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/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
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

DescriptionCVE.org

The Super Forms - Drag & Drop Form Builder plugin for WordPress is vulnerable to Arbitrary Directory Deletion in all versions up to, and including, 6.3.316 via the submit_form function. This is due to insufficient validation of attacker-controlled JSON field declarations against the actual form schema, combined with a non-effective ABSPATH guard that dirname() trivially bypasses by stripping the trailing slash. This makes it possible for unauthenticated attackers to recursively delete arbitrary directories on the server, including the WordPress root directory. Exploitation requires that an administrator has enabled the 'Delete files from server after form submissions' setting, though this is a documented and commonly-enabled feature.

Executive ViewAI

Why It Matters

A critical flaw in the Super Forms - Drag & Drop Form Builder plugin (all versions through 6.3.316) allows any remote, unauthenticated party to recursively delete arbitrary directories on a WordPress server, including the site's installation root. Because the vulnerability can only be reached when an administrator has enabled the plugin's 'Delete files from server after form submissions' option, exposure is limited to sites using that setting - but for those sites the outcome is total loss of the website, its content, and any locally hosted data. With no vendor patch available, leadership should treat this as an immediate availability and data-loss risk requiring plugin removal or reconfiguration rather than a routine update.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: disable the 'Delete files from server after form submissions' setting, which is a prerequisite for reaching the vulnerable code path; deactivate or uninstall Super Forms versions up to and including 6.3.316 on internet-facing sites; apply WAF or virtual-patching rules that block crafted JSON field declarations submitted to the submit_form function; maintain tested offline or immutable backups; and enable file-integrity monitoring with alerting on bulk or recursive directory deletions.

Threat Intelligence Overview

EPSS Score
0.3%
Top 78% exploitable
Prevalence
Medium
popular commercial WordPress form plugin, but gated behind non-default deletion setting
Social Media
3
Sightings
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 CRITICAL
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
CRITICAL severity
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
Yes
Human Impact
High
Technical Impact
Partial

Priority Score

46
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +46
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.

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