# CVE-2025-14842: Drag and Drop Multiple File Upload – Contact Form 7 <= 1.3.9.2 - Unauthenticated Limited Arbitrary File Upload


- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 7 Jan 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-f8vf-66gm-85xg

## What is CVE-2025-14842?

CVE-2025-14842 is a medium-severity vulnerability in glenwpcoder Drag and Drop Multiple File Upload for Contact Form 7, published on 7 Jan 2026. 

### Official description

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.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2025-14842?


## How do I fix CVE-2025-14842?

No fix has been published for CVE-2025-14842 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-14842 being exploited?

There is no known exploitation of CVE-2025-14842 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-14842 and fix it if it is affected.

What it is: CVE-2025-14842 is a medium-severity vulnerability in glenwpcoder Drag and Drop Multiple File Upload for Contact Form 7, published on 7 Jan 2026. 
Exploitation: There is no known exploitation of CVE-2025-14842 in the wild and no public exploit code.

Affected product: glenwpcoder Drag and Drop Multiple File Upload for Contact Form 7. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-14842/ (Markdown: https://insights.sbomify.com/CVE-2025-14842/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-14842
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-14842
- OSV: https://osv.dev/vulnerability/CVE-2025-14842

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-14842/
Summaries are generated and may contain mistakes; the official description above is the record.