On this page

Atomicorp WAF Research Note: CVE-2026-14894

WordPress Super Forms <= 6.3.313 - Arbitrary File Upload

CVE Details

Status: Attack Blocked by Atomicorp
  • Already protected by existing Atomicorp WAF rules
  • Protection status: Understanding Atomicorp WAF Protection Status
  • CVE: CVE-2026-14894
  • Name: WordPress Super Forms <= 6.3.313 - Arbitrary File Upload
  • Severity: Critical
  • CVSS: 9.8 (v3.1) (Critical)
  • CVSS version: 3.1
  • CVSS source: Wordfence CNA
  • CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
    • Attack vector: Network
    • Attack complexity: Low
    • Privileges required: None
    • User interaction: None
    • Scope: Unchanged
    • Confidentiality impact: High
    • Integrity impact: High
    • Availability impact: High
  • CWE: CWE-434 — Unrestricted Upload of File with Dangerous Type
  • Related CAPEC attack patterns (via MITRE CWE relationships): CAPEC-1
  • Vendor: developer-developer
  • Vulnerable products: Super Forms – Drag & Drop Form Builder , super-forms
  • CVE published: 2026-07-10
  • CVE last modified: 2026-07-10
  • EPSS: 0.0527; 92.1th percentile (FIRST )
  • Latest Update: 2026-09-06
  • Selected Rule IDs observed: 340748
  • Matching rules: 1; rules with blocking actions: 1
  • Would-block Rule IDs: 340748
  • Request surfaces inspected: JSON request data, Request URI, Request arguments, SOAP request data

Vulnerability Description

The Super Forms – Drag & Drop Form Builder plugin for WordPress is vulnerable to Arbitrary File Upload in all versions up to, and including, 6.3.313 via the submit_form function. This is due to missing file type validation and the absence of any capability check on the submit_form nopriv AJAX handler, whose only barrier is a session nonce freely obtainable by unauthenticated visitors via a separate nopriv endpoint. This makes it possible for unauthenticated attackers to upload files that may be executable, which makes remote code execution possible. The nonce requirement is trivially bypassed because the super_create_nonce nopriv AJAX action allows any unauthenticated visitor to mint a valid sf_nonce and session cookie in a single prior request, reducing exploitation to two unauthenticated HTTP requests.

  1. Maintain the observed Atomicorp protections. Keep your Atomicorp commercial rules current and confirm that the selected observed rules (340748 ) have not been locally disabled. Atomicorp commercial rules are enabled by default. If you use Atomic WAF, review the applicable policy and rule settings.

  2. Apply the vendor’s remediation. WAF protection is defense in depth and does not replace upgrading or following the affected vendor’s guidance.

    • Affected versions: WebRehab Super Forms – Drag & Drop Form Builder versions through 6.3.313.
    • No specific CNA/vendor solution or workaround is included in the current CVE Record . Review the vendor’s security advisories and supported-release guidance before making changes.

  3. Validate after changes. Confirm rule updates are current, review WAF events for the affected application, and test application behavior after vendor upgrades, mitigations, or local policy changes.

Research Notes

Atomicorp WAF protections are designed around attack techniques and exploit behaviors, allowing existing protections to apply across multiple vulnerabilities without requiring a unique rule for every CVE.

Public Vulnerability References

Test or Research Source

Research Note Context

This research note documents exploit-technique analysis associated with this vulnerability and references Atomicorp WAF protections observed during engineering review, testing, or validation activities.

Atomicorp security controls are generally designed to identify and mitigate attack techniques and exploit behaviors rather than individual CVE identifiers. As a result, protections developed for one vulnerability may also apply to related attack variants and future vulnerabilities using similar techniques.

Learn More

Atomicorp develops commercially supported security technologies for web applications, servers, endpoints, workloads, and legacy enterprise platforms.

Organizations interested in protecting systems against exploit techniques associated with vulnerabilities such as this one can learn more about:

  • Atomic ModSecurity Rules: commercially maintained WAF rules for ModSecurity deployments, including protections for web attacks, bots, scanners, malware, exploitation attempts, and emerging vulnerability classes.
  • Atomic WAF: an enterprise web application firewall with Atomicorp rules, centralized management, reporting, authentication controls, and operational tooling.
  • Atomic ModSecurity Integrator: a special licensing option for MSPs, MSSPs, OEMs, VARs, reverse proxy providers, and other integrators who want to incorporate Atomicorp ModSecurity rule technology into their own products or services.
  • Atomic OSSEC: an enterprise OSSEC-based intrusion detection, compliance, and security monitoring platform.
  • Atomic Protector: workload protection for Linux, web, cloud, data center, and hybrid environments.

For additional information, product evaluations, or technical discussions, visit https://www.atomicorp.com/ or https://modsecurity.io/ .