dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-5710

HIGH · 7.5 CVSS v3.1 Published 2026-04-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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 for Contact Form 7 plugin for WordPress is vulnerable to Path Traversal leading to Arbitrary File Read in versions up to and including 1.3.9.6. This is due to the plugin using client-supplied mfile[] POST values as the source of truth for email attachment selection without performing any server-side upload provenance check, path canonicalization, or directory containment boundary enforcement. In dnd_wpcf7_posted_data(), each user-submitted filename is directly appended to the plugin's upload URL without sanitization. In dnd_cf7_mail_components(), the URL is converted back to a filesystem path using str_replace() and only file_exists() is used as the acceptance check before attaching the file to the outgoing CF7 email. This makes it possible for unauthenticated attackers to read and exfiltrate arbitrary files readable by the web server process via path traversal sequences in the mfile[] parameter, with files being disclosed as email attachments. Note: This vulnerability is limited to the 'wp-content' folder due to the wpcf7_is_file_path_in_content_dir() function in the Contact Form 7 plugin.

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 Contact Form 7 Drag and Drop Multiple File Upload plugin is vulnerable to Path Traversal allowing unauthenticated arbitrary file read. The plugin uses client-supplied mfile[] POST values as filenames without sanitization, canonicalization, or directory containment checks. In dnd_wpcf7_posted_data(), filenames are directly appended to upload URLs, and in dnd_cf7_mail_components(), str_replace() converts URLs to filesystem paths with only file_exists() as validation. Attackers can read arbitrary files readable by the web server via path traversal sequences, delivered as email attachments, though limited to wp-content folder by CF7's containment function.

MitigationUpdate to patched version when available; until then, disable the plugin or deploy WAF rules blocking path traversal patterns (../, etc.) in mfile[] parameters and ensure contact form email receipts require authentication or are restricted to trusted recipients.

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
None
Availability
None

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

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 plugin installation
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Drag and Drop Multiple File Upload Contact Form 7' or similar. Alternatively, check the wp-content/plugins directory for folders containing 'dnd-cf7' or 'drag-drop' in the name.
    Affected if The plugin is installed and active
  2. Identify plugin version
    In WordPress admin Plugins list, click on the plugin name to view details and note the installed version number. Compare this against any known affected version ranges for this CVE.
    Affected if Installed version falls within the affected version range
  3. Check for active file upload forms
    In WordPress admin, go to Contact > Contact Forms and examine each form. Look for fields that use the plugin's file upload functionality, typically indicated by 'drag and drop' or 'multiple' file upload tags in the form editor.
    Affected if Any contact form is configured to use the plugin's file upload feature
  4. Inspect for vulnerable parameter exposure
    Examine your web server logs (access logs) for incoming POST requests containing the mfile[] parameter, especially those with path traversal sequences such as ../ patterns.
    Affected if Requests with mfile[] parameter containing ../ sequences are being processed
  5. Verify email receipt configuration
    Check the contact form's Mail settings to confirm if file attachments are included in email notifications. The vulnerability delivers arbitrary files as email attachments.
    Affected if Forms are configured to send file attachments via email

If the plugin is installed and any contact form uses its file upload feature, the environment may be vulnerable to unauthenticated path traversal attacks via mfile[] parameters.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to patched version when available; until then, disable the plugin or deploy WAF rules blocking path traversal patterns (../, etc.) in mfile[] parameters and ensure contact form email receipts require authentication or are restricted to trusted recipients.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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