dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-14842

MEDIUM · 6.1 CVSS v3.1 Published 2026-01-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 limited upload of files with a dangerous type in all versions up to, and including, 1.3.9.2. This is due to the plugin not blocking .phar and .svg files. This makes it possible for unauthenticated attackers to upload arbitrary .phar or .svg files containing malicious PHP or JavaScript code. Malicious PHP code can be used to achieve remote code execution on the server via direct file access, if the server is configured to execute .phar files as PHP. The upload of .svg files allows for Stored Cross-Site Scripting under certain circumstances.

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 WordPress plugin fails to validate uploaded file types, allowing unauthenticated attackers to upload .phar files (potentially leading to RCE if the server executes .phar as PHP) and .svg files (containing malicious JavaScript for stored XSS).

MitigationUpdate the plugin to version 1.3.9.3 or later which implements proper file type blocking for .phar and .svg extensions. If immediate update is not possible, consider disabling the file upload functionality or implementing web-server-level restrictions on .phar and .svg file uploads.

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 the vulnerable plugin is installed
    Check for 'Drag and Drop Multiple File Upload - Contact Form 7' in the WordPress plugins directory (wp-content/plugins/) or run: wp plugin list --search='drag-and-drop-multiple-file-upload'
    Affected if Plugin is present in the WordPress installation
  2. Identify the installed plugin version
    Read the version number from the plugin's main PHP file header in wp-content/plugins/drag-and-drop-multiple-file-upload-contact-form-7/
    Affected if Version is below 1.3.9.3 (vulnerable versions)
  3. Check if file upload functionality is active
    Search WordPress content for the plugin shortcode (commonly [drag-and-drop-file-upload] or similar) or inspect Contact Form 7 forms that have file attachment fields enabled
    Affected if Any forms with the plugin's file upload feature are published or active
  4. Inspect upload directory for malicious file types
    List files in the WordPress uploads folder: find wp-content/uploads/ -type f \( -name '*.phar' -o -name '*.svg' \) -mtime -30
    Affected if Any .phar or .svg files were recently uploaded (indicating potential exploitation)

Environment is affected if the plugin version is below 1.3.9.3 AND the file upload feature is enabled or in use on the site

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.9.3 or later which implements proper file type blocking for .phar and .svg extensions. If immediate update is not possible, consider disabling the file upload functionality or implementing web-server-level restrictions on .phar and .svg file uploads.

Recommended fix Moderate confidence

1.3.9.3 or later (latest version)

  1. Check the WordPress plugin repository for the latest version of 'Drag and Drop Multiple File Upload – Contact Form 7'
  2. Update the plugin to the latest available version (after 1.3.9.2)
  3. Verify the update was successful in Plugins > Installed Plugins
  4. If available, review the plugin's changelog to confirm the security fix for .phar and .svg file upload restriction is included
  5. Ensure the web server is not configured to execute .phar files as PHP as a defense-in-depth measure

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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