Skip to main content

PHP CVE-2025-3515

| EUVDEUVD-2025-18492 HIGH
Unrestricted Upload of File with Dangerous Type (CWE-434)
2025-06-17 security@wordfence.com
8.1
CVSS 3.1 · NVD
View

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V5 - File Handling File type validation, storage isolation
MITRE ATT&CK

2 techniques across 2 tactics: Command and Control, Persistence

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Impact

CVSS 8.1 (High) with AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H reflects a network-accessible vulnerability requiring no authentication but with high attack complexity (likely dependent on server configuration). The AC:H factor correctly identifies that exploitation requires a specific Apache+mod_php configuration—not all WordPress hosts are vulnerable. However, this configuration is extremely common in shared hosting environments, meaning real-world impact is significant. The CVSS vector appropriately assigns maximum impact ratings (C:H/I:H/A:H) given that RCE allows full system compromise. Without explicit KEV status or EPSS score data provided, the risk assessment relies on attack vector analysis: unauthenticated, network-accessible, public disclosure in plugin ecosystem context, and a widely-adopted affected plugin create substantial real-world risk despite AC:H. This is a genuine priority vulnerability for any WordPress site using this plugin, particularly on standard hosting configurations. Organizations should treat this as critical given the ubiquity of both WordPress and default Apache deployments.

Exploit ScenarioDerived

An attacker identifies a WordPress site using the vulnerable Drag and Drop Multiple File Upload for Contact Form 7 plugin (version ≤1.3.8.9). The attacker crafts a malicious .phar file containing PHP code that establishes a web shell (e.g., spawning a reverse shell or persistent backdoor). The attacker submits the contact form with the .phar file attachment, bypassing the plugin's blacklist check because .phar is not in the blocked extensions list. The file is uploaded to the WordPress uploads directory (typically /wp-content/uploads/). The attacker then directly accesses the uploaded .phar file via HTTP (e.g., http://target.com/wp-content/uploads/2025/01/shell.phar). Apache's mod_php interprets the .phar file as PHP code and executes it. The attacker gains remote code execution, allowing them to read/modify database credentials, exfiltrate sensitive data, install persistent backdoors, or pivot to other systems on the network. Attack complexity is rated High because success depends on the server running Apache with mod_php (not NGINX, not PHP-FPM without script handling), but this configuration is widespread in default WordPress hosting, making the vulnerability highly practical despite the AC:H rating.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 4.6% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 14, 2026

The Drag and Drop Multiple File Upload for Contact Form 7 WordPress plugin (versions ≤1.3.8.9) contains an unrestricted file upload vulnerability allowing unauthenticated attackers to bypass file type blacklists and upload dangerous file extensions (.phar, etc.). On servers configured to execute .phar files as PHP (common in default Apache+mod_php setups), this enables remote code execution with high impact to confidentiality, integrity, and availability (CVSS 8.1). While KEV and EPSS data are not provided, the vulnerability is actively exploitable given its public disclosure and network-accessible attack vector.

RemediationAI

Immediate Actions: (1) Update the Drag and Drop Multiple File Upload for Contact Form 7 plugin to version 1.3.9.0 or later, which should include corrected file type validation logic; (2) If an immediate patch is unavailable, disable the plugin entirely until a patched version is released; (3) Review and remove any suspicious files uploaded via the affected form fields, particularly .phar, .php, .phtml, .php3, .php4, .php5, .pht, and other PHP-executable extensions. Longer-term Mitigations: (1) Implement a strict whitelist of allowed file types (e.g., .pdf, .doc, .docx, .jpg, .png) rather than relying on blacklists; (2) Add .htaccess rule to prevent script execution in upload directories: <FilesMatch "\.ph(p[3-6]?|tml|ar)"> with Deny from all; (3) Store uploaded files outside the web root if possible; (4) Configure PHP to disable execution of uploaded files via php.ini settings; (5) Implement server-level Content-Type validation. Contact the plugin developer (WPEverest or relevant maintainer based on WordPress.org plugin repository) for official patch release timeline and advisory.

Affected VersionsENISA

Drag and Drop Multiple File Upload for Contact Form 7 * ≤1.3.8.9

Affected Packages

euvd drag_and_drop_multiple_file_upload_for_contact_form_7 no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

This vulnerability stems from CWE-434 (Unrestricted Upload of File with Dangerous Type), a fundamental file upload validation flaw. The plugin implements a blacklist-based approach to filter dangerous file types, but the implementation is insufficient—likely checking only against a limited set of extensions while failing to account for alternate executable formats like .phar (PHP Archive files). On Apache servers with mod_php enabled, the PHP interpreter processes .phar files as executable PHP code by default, converting a file upload vulnerability into arbitrary code execution. The attack is possible because: (1) the plugin does not use a strict whitelist of safe extensions; (2) it lacks proper Content-Type validation; (3) it does not disable script execution in upload directories via .htaccess or equivalent; and (4) it does not implement file permission restrictions or sandboxing. Contact Form 7 is one of WordPress's most widely deployed plugins, making integrations like this file upload add-on high-value attack targets.

Know when PHP gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 8.1 HIGH
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
Patch released
Mar 14, 2026 - 22:15 nvd
Patch available
CVE Published
Jun 17, 2025 - 10:15 nvd
HIGH 8.1

DescriptionCVE.org

The Drag and Drop Multiple File Upload for Contact Form 7 plugin for WordPress is vulnerable to arbitrary file uploads due to insufficient file type validation in all versions up to, and including, 1.3.8.9. This makes it possible for unauthenticated attackers to bypass the plugin's blacklist and upload .phar or other dangerous file types on the affected site's server, which may make remote code execution possible on the servers that are configured to handle .phar files as executable PHP scripts, particularly in default Apache+mod_php configurations where the file extension is not strictly validated before being passed to the PHP interpreter.

Executive ViewAI

Why It Matters

WordPress sites using the Drag and Drop Multiple File Upload for Contact Form 7 plugin (versions up to 1.3.8.9) face critical risk of unauthorized file uploads and potential server compromise. Unauthenticated attackers can exploit insufficient file validation to execute malicious code, requiring immediate remediation across all affected installations.

Business Impact: High
Compensating Controls

Apply vendor patch. If immediate patching is unavailable: disable the file upload functionality in the plugin settings, implement WAF rules to block .phar file uploads, configure Apache to prevent PHP execution in upload directories, enable strict file type validation at the web server level, and restrict file upload permissions to non-executable directories.

Threat Intelligence Overview

EPSS Score
4.6%
Top 11% exploitable
Exploit
POC
Public exploit code exists
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC Yes
EPSS 4.6%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
Poc
System Exposure· derived
Open
Automatable· derived
No
Human Impact
High

Priority Score

65
Low Medium High Critical
KEV: 0
EPSS: +5
CVSS: +40
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Code Injection CRITICAL

Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

More in PHP

View all
CVE-2019-11043 CRITICAL POC
9.8 Oct 28

In PHP versions 7.1.x below 7.1.33, 7.2.x below 7.2.24 and 7.3.x below 7.3.11 in certain configurations of FPM setup it

CVE-2012-1823 CRITICAL POC
9.8 May 11

sapi/cgi/cgi_main.c in PHP before 5.3.12 and 5.4.x before 5.4.2, when configured as a CGI script (aka php-cgi), does not

CVE-2016-1555 CRITICAL POC
9.8 Apr 21

(1) boardData102.php, (2) boardData103.php, (3) boardDataJP.php, (4) boardDataNA.php, and (5) boardDataWW.php in Netgear

CVE-2018-11138 CRITICAL POC
9.8 May 31

The '/common/download_agent_installer.php' script in the Quest KACE System Management Appliance 8.0.318 is accessible by

CVE-2024-11680 CRITICAL POC
9.8 Nov 26

ProjectSend versions prior to r1720 are affected by an improper authentication vulnerability. Rated critical severity (C

CVE-2025-49113 CRITICAL POC
9.9 Jun 02

Roundcube Webmail contains a critical PHP object deserialization vulnerability (CVE-2025-49113, CVSS 9.9) that allows au

CVE-2017-9841 CRITICAL POC
9.8 Jun 27

Util/PHP/eval-stdin.php in PHPUnit before 4.8.28 and 5.x before 5.6.3 allows remote attackers to execute arbitrary PHP c

CVE-2025-0108 HIGH POC
8.8 Feb 12

Palo Alto Networks PAN-OS management web interface contains an authentication bypass allowing unauthenticated attackers

CVE-2021-25298 HIGH POC
8.8 Feb 15

Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re

CVE-2021-25296 HIGH POC
8.8 Feb 15

Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re

CVE-2013-4983 CRITICAL POC
10.0 Sep 10

The get_referers function in /opt/ws/bin/sblistpack in Sophos Web Appliance before 3.7.9.1 and 3.8 before 3.8.1.1 allows

CVE-2023-6553 CRITICAL POC
9.8 Dec 15

The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy