dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2026-3459

HIGH · 8.1 CVSS v3.1 Published 2026-03-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 Drag and Drop Multiple File Upload - Contact Form 7 plugin for WordPress is vulnerable to arbitrary file uploads due to insufficient file type validation in the 'dnd_upload_cf7_upload' function in versions up to, and including, 1.3.7.3. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible. This can be exploited if the form includes a multiple file upload field with ‘*’ as the accepted file type.

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 Drag and Drop Multiple File Upload - Contact Form 7 plugin for WordPress versions up to 1.3.7.3 contains an arbitrary file upload vulnerability in the 'dnd_upload_cf7_upload' function. The plugin fails to properly validate file types when a form field uses '*' as the accepted file type, allowing unauthenticated attackers to upload executable files directly to the server and potentially achieve remote code execution.

MitigationUpdate the plugin to version 1.3.7.4 or later. If immediate patching is not possible, disable file upload forms using '*' as the accepted file type or consider disabling the plugin until an update can be applied.

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/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. Verify plugin is installed
    Check WordPress plugins directory or wp-admin for 'Drag and Drop Multiple File Upload - Contact Form 7' plugin and note its version number
    Affected if Plugin is installed and version is 1.3.7.3 or lower
  2. Confirm affected version range
    Compare installed version to affected range: versions up to and including 1.3.7.3 are vulnerable; version 1.3.7.4 and later are fixed
    Affected if Installed version is 1.3.7.3 or lower
  3. Identify forms using wildcard file type
    Review Contact Form 7 forms and look for file upload fields where the accepted file type is set to '*' or contains '*' in the allowed types
    Affected if Any active form uses '*' as the accepted file type, allowing any file extension to be uploaded
  4. Check uploaded file location and accessibility
    Locate the upload directory (typically /wp-content/uploads/dnd_cf7_uploads/ or similar) and verify if files are served from a web-accessible path without execution prevention
    Affected if Uploaded files are stored in a web-accessible directory without proper execution guards, making uploaded executables directly accessible

User is affected if the plugin version is 1.3.7.3 or lower AND any form uses '*' as the accepted file type, allowing unauthenticated arbitrary file upload.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 1.3.7.4 or later. If immediate patching is not possible, disable file upload forms using '*' as the accepted file type or consider disabling the plugin until an update can be applied.

Recommended fix Moderate confidence

Version higher than 1.3.7.3 (check plugins.trac.wordpress.org for the latest fixed release)

  1. Navigate to the WordPress admin dashboard and go to Plugins > Installed Plugins
  2. Locate 'Drag and Drop Multiple File Upload - Contact Form 7' in the plugin list
  3. Check the current installed version - if it is 1.3.7.3 or lower, the site is vulnerable
  4. Deactivate and delete the vulnerable plugin version
  5. Visit the official WordPress plugin repository at plugins.trac.wordpress.org to check for a newer version that addresses this vulnerability
  6. If a fixed version (higher than 1.3.7.3) is available, install it via WordPress admin or upload manually
  7. If no fixed version is available, consider alternative plugins for file upload functionality
  8. After updating, verify that file upload fields do NOT use '*' as the accepted file type - restrict to specific allowed extensions only
Caveat Review form configurations after upgrade as file upload field settings may need adjustment to remove wildcard '*' file type acceptance

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3459 — 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-3459 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