dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2026-14894

CRITICAL · 9.8 CVSS v3.1 Published 2026-07-10
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Super Forms WordPress plugin allows unauthenticated file upload via the submit_form AJAX handler due to missing file type validation and capability checks. The nonce protection is trivially bypassed by first calling the super_create_nonce nopriv endpoint to obtain a valid session cookie and nonce, then using these credentials to upload executable files in a second request, achieving remote code execution.

MitigationImmediately disable or remove the Super Forms plugin if not patched to a version beyond 6.3.313. Audit the uploads directory for suspicious files and consider the site compromised—reset credentials and perform a full forensic review.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Super Forms plugin is installed
    Check WordPress admin > Plugins page for Super Forms, or inspect /wp-content/plugins/super-forms/ directory existence
    Affected if Super Forms plugin is present on the WordPress site
  2. Determine installed Super Forms version
    View the plugin version in the WordPress plugins admin page, or open /wp-content/plugins/super-forms/plugin.php and locate the Version header in the plugin comment block
    Affected if Installed version is 6.3.313 or earlier (versions beyond 6.3.313 are patched)
  3. Test unauthenticated nonce endpoint accessibility
    Send a GET request to /wp-admin/admin-ajax.php?action=super_create_nonce (the nopriv endpoint) without any authentication cookies; observe if the response returns a valid nonce and sets a session cookie
    Affected if The endpoint responds with a valid nonce and session cookie without requiring login
  4. Audit uploads directory for suspicious files
    Use FTP, SSH, or WordPress file manager to examine /wp-content/uploads/ and subdirectories; search for .php, .phtml, .phar, .exe, .js, or other unexpected file types that may indicate uploaded webshells
    Affected if Executable or script files are found in the uploads directory that were not intentionally uploaded through WordPress

The environment is affected if Super Forms version 6.3.313 or lower is installed AND the AJAX endpoints are accessible without authentication (can obtain nonce via the nopriv handler).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Immediately disable or remove the Super Forms plugin if not patched to a version beyond 6.3.313. Audit the uploads directory for suspicious files and consider the site compromised—reset credentials and perform a full forensic review.

Recommended fix Moderate confidence

Update to the version containing the fix from commit c5838f5877c72b738c54ed970935c77ae6830c3a (contact vendor for exact version number)

  1. Navigate to the Super Forms plugin directory in the WordPress installation (wp-content/plugins/super-forms/)
  2. Review the vendor patch commit at https://github.com/RensTillmann/super-forms/commit/c5838f5877c72b738c54ed970935c77ae6830c3a to understand the code changes
  3. Apply the vendor patch which adds proper file type validation and capability checks to the submit_form function
  4. Alternatively, replace the super-forms plugin files with the latest version from the official WordPress plugin repository after the fix is released
  5. Verify that the super_create_nonce endpoint no longer allows unauthenticated minting of valid nonces for the submit_form action
  6. Test that file uploads are now properly validated and restricted to safe file types

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-14894 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-14894 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data