/

CVE-2026-14894

Severity:

CRITICAL RISK

(9.8)

Arbitrary File Upload (CWE-434) in Super Forms Plugin

CVE-2026-14894

Deferred

Vulnerability type

Category:

Arbitrary File Upload

CWE:

CWE-434

Impact:

Remote Code Execution

Severity:

CRITICAL RISK

(9.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

The Super Forms – Drag & Drop Form Builder plugin for WordPress allows unauthenticated arbitrary file uploads through its submit_form AJAX handler.

Because file types are not validated and nonce creation is exposed to unauthenticated users, attackers can upload executable files, leading to potential remote code execution on the WordPress host.

Affected context

This vulnerability occurs in WordPress sites that have the Super Forms – Drag & Drop Form Builder plugin enabled and expose its nopriv AJAX endpoints to the public.

It manifests when the submit_form handler accepts file uploads without enforcing strict type and capability checks, and when nonce generation is available to unauthenticated visitors.

In such deployments, uploaded files may be stored in web-accessible locations where the server will interpret certain file types as executable code.

Exploit preconditions

  • Attack surface: Public-facing WordPress AJAX endpoints tied to the Super Forms plugin
  • Required access: No authentication required; any external visitor can interact with nopriv actions
  • Trigger point: Invoking the submit_form function with a crafted file upload after obtaining a valid sf_nonce and session cookie
  • Why exploitation is possible: The submit_form handler lacks capability checks and robust file type validation, while the super_create_nonce action allows arbitrary nonce and session creation, effectively removing meaningful access control barriers

Why this happens

The underlying bug aligns with CWE-434: Unrestricted Upload of File with Dangerous Type.

The plugin's submit_form function accepts user-supplied files without rigorously validating MIME type, extension, or content, and does not enforce permissions on its nopriv AJAX handler.

Additionally, nonce generation is exposed via another unauthenticated endpoint, meaning the nominal protection mechanism can be trivially satisfied by any visitor.

This combination of weak input controls and missing authorization checks creates a pattern where untrusted clients can place potentially executable files into locations processed by the server.

Potential impact

  • Upload and execution of arbitrary server-side code
  • Full compromise of the WordPress site and its database
  • Use of the compromised site for malware hosting or phishing
  • Lateral movement within the hosting environment, depending on server configuration
  • Defacement, data theft, or destruction of site content

General mitigation guidance

Effective mitigation focuses on tightening upload and authorization patterns rather than relying on ad hoc checks.

Common defensive approaches include:

  • Enforcing strict server-side validation of file extensions, MIME types, and content, allowing only a minimal set of benign formats
  • Storing uploaded files in non-executable directories and disabling script execution in upload paths at the web server level
  • Requiring capability checks and robust access control for all file-handling AJAX endpoints, especially those marked as nopriv
  • Treating nonces and similar tokens as supplementary protections, not primary access control mechanisms, and ensuring they cannot be minted by unauthenticated users
  • Applying least-privilege principles to file system and PHP execution permissions to limit the blast radius of any misconfigured upload feature

How teams detect issues like this

Detection typically combines code-centric and operational approaches:

  • Static analysis rules that flag upload handlers lacking capability checks, file type validation, and safe storage paths
  • Code review practices that scrutinize nopriv AJAX actions, nonce generation endpoints, and any direct use of user-supplied file names or paths
  • Runtime monitoring for unexpected executable files appearing in upload directories or unusual requests to newly created files
  • Web application firewall policies that inspect multipart/form-data requests and block uploads of dangerous file types
  • Periodic security scanning of plugins and custom code to identify unrestricted file upload patterns

Sources

SourceLink
github.comgithub.com/RensTillmann/super-forms/commit/c5838f5877c72b738c54ed970935c77ae6830c3a
wordfence.comwordfence.com/threat-intel/vulnerabilities/id/e9c7fb16-efbb-41e9-be13-98e96c1e9100?source=cve

Frequently asked

questions

Yes. Because both the nonce generation and file upload handlers are exposed as nopriv AJAX actions, an attacker does not need an account to exploit the issue.

Successful exploitation can allow execution of attacker-controlled code in the context of the web server, which often means full control over the WordPress site and access to its data, subject to hosting and OS-level permissions.

The most robust fix pattern is to strictly validate uploaded files, store them in non-executable locations, and ensure that all upload-related endpoints enforce proper capability checks and cannot be triggered by unauthenticated visitors.

Design upload features with a default-deny stance: allow only necessary, benign file types; implement layered validation and content checks; enforce strong authorization on all file-handling APIs; and configure the web server so that upload directories cannot execute code even if validation fails.

Find out what's already
exploitable in your codebase.