CVE-2025-14842: CWE-434 Unrestricted Upload of File with Dangerous Type in glenwpcoder Drag and Drop Multiple File Upload for Contact Form 7
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.
AI Analysis
Technical Summary
The vulnerability identified as CVE-2025-14842 affects the 'Drag and Drop Multiple File Upload for Contact Form 7' WordPress plugin developed by glenwpcoder. This plugin, widely used to facilitate multiple file uploads in Contact Form 7, improperly restricts file types during upload, specifically failing to block .phar and .svg files. The core issue is classified under CWE-434: Unrestricted Upload of File with Dangerous Type. Attackers can exploit this by uploading malicious .phar files containing PHP code or .svg files containing JavaScript payloads. If the web server is configured to execute .phar files as PHP scripts, this can lead to remote code execution (RCE), allowing attackers to execute arbitrary code on the server, potentially taking full control. The .svg files can be used to store malicious JavaScript, leading to stored cross-site scripting (XSS) attacks, which can compromise user sessions or redirect users to malicious sites. The vulnerability requires no authentication, increasing its risk, but user interaction is needed to trigger the XSS payload. The CVSS v3.1 score is 6.1 (medium severity), reflecting network attack vector, low attack complexity, no privileges required, and user interaction needed, with impact on confidentiality and integrity but not availability. No patches are currently linked, and no known exploits have been observed in the wild. The vulnerability affects all versions up to and including 1.3.9.2 of the plugin.
Potential Impact
This vulnerability poses significant risks to organizations using the affected WordPress plugin. Successful exploitation can lead to remote code execution, which is one of the most severe impacts, potentially allowing attackers to fully compromise the web server, access sensitive data, deploy malware, or pivot to internal networks. The stored XSS vulnerability can be leveraged to hijack user sessions, steal credentials, or perform phishing attacks against site visitors. Since the vulnerability is exploitable without authentication, any internet-facing WordPress site using this plugin is at risk. The impact extends to website integrity, confidentiality of data, and user trust. Organizations relying on Contact Form 7 with this plugin may face data breaches, defacement, or service disruptions. The lack of known exploits in the wild suggests limited active exploitation currently, but the ease of exploitation and severity of potential outcomes warrant urgent attention.
Mitigation Recommendations
1. Immediate mitigation involves disabling or removing the vulnerable plugin until a patch is available. 2. If removal is not feasible, restrict file upload types by implementing server-side validation to explicitly block .phar and .svg files. 3. Configure the web server to never execute .phar files as PHP scripts, for example, by disabling PHP execution in upload directories or using strict MIME type checks. 4. Employ a Web Application Firewall (WAF) to detect and block malicious file uploads and suspicious requests targeting the plugin. 5. Monitor web server logs for unusual file upload activity or access to .phar and .svg files. 6. Educate site administrators on the risks of installing unverified plugins and maintaining up-to-date software. 7. Once available, promptly apply official patches from the plugin vendor. 8. Conduct regular security audits and penetration testing focusing on file upload functionalities. These steps go beyond generic advice by focusing on configuration hardening and proactive monitoring tailored to this vulnerability.
Affected Countries
United States, Germany, United Kingdom, Canada, Australia, France, Netherlands, India, Brazil, Japan
CVE-2025-14842: CWE-434 Unrestricted Upload of File with Dangerous Type in glenwpcoder Drag and Drop Multiple File Upload for Contact Form 7
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability identified as CVE-2025-14842 affects the 'Drag and Drop Multiple File Upload for Contact Form 7' WordPress plugin developed by glenwpcoder. This plugin, widely used to facilitate multiple file uploads in Contact Form 7, improperly restricts file types during upload, specifically failing to block .phar and .svg files. The core issue is classified under CWE-434: Unrestricted Upload of File with Dangerous Type. Attackers can exploit this by uploading malicious .phar files containing PHP code or .svg files containing JavaScript payloads. If the web server is configured to execute .phar files as PHP scripts, this can lead to remote code execution (RCE), allowing attackers to execute arbitrary code on the server, potentially taking full control. The .svg files can be used to store malicious JavaScript, leading to stored cross-site scripting (XSS) attacks, which can compromise user sessions or redirect users to malicious sites. The vulnerability requires no authentication, increasing its risk, but user interaction is needed to trigger the XSS payload. The CVSS v3.1 score is 6.1 (medium severity), reflecting network attack vector, low attack complexity, no privileges required, and user interaction needed, with impact on confidentiality and integrity but not availability. No patches are currently linked, and no known exploits have been observed in the wild. The vulnerability affects all versions up to and including 1.3.9.2 of the plugin.
Potential Impact
This vulnerability poses significant risks to organizations using the affected WordPress plugin. Successful exploitation can lead to remote code execution, which is one of the most severe impacts, potentially allowing attackers to fully compromise the web server, access sensitive data, deploy malware, or pivot to internal networks. The stored XSS vulnerability can be leveraged to hijack user sessions, steal credentials, or perform phishing attacks against site visitors. Since the vulnerability is exploitable without authentication, any internet-facing WordPress site using this plugin is at risk. The impact extends to website integrity, confidentiality of data, and user trust. Organizations relying on Contact Form 7 with this plugin may face data breaches, defacement, or service disruptions. The lack of known exploits in the wild suggests limited active exploitation currently, but the ease of exploitation and severity of potential outcomes warrant urgent attention.
Mitigation Recommendations
1. Immediate mitigation involves disabling or removing the vulnerable plugin until a patch is available. 2. If removal is not feasible, restrict file upload types by implementing server-side validation to explicitly block .phar and .svg files. 3. Configure the web server to never execute .phar files as PHP scripts, for example, by disabling PHP execution in upload directories or using strict MIME type checks. 4. Employ a Web Application Firewall (WAF) to detect and block malicious file uploads and suspicious requests targeting the plugin. 5. Monitor web server logs for unusual file upload activity or access to .phar and .svg files. 6. Educate site administrators on the risks of installing unverified plugins and maintaining up-to-date software. 7. Once available, promptly apply official patches from the plugin vendor. 8. Conduct regular security audits and penetration testing focusing on file upload functionalities. These steps go beyond generic advice by focusing on configuration hardening and proactive monitoring tailored to this vulnerability.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2025-12-17T17:58:42.026Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 695e0293a55ed4ed9984d532
Added to database: 1/7/2026, 6:52:03 AM
Last enriched: 2/27/2026, 11:37:44 AM
Last updated: 3/25/2026, 4:39:48 AM
Views: 111
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.