CVE-2025-14390: CWE-434 Unrestricted Upload of File with Dangerous Type in videomerchant Video Merchant
The Video Merchant plugin for WordPress is vulnerable to Cross-Site Request Forgery in version <= 5.0.4. This is due to missing or incorrect nonce validation on the video_merchant_add_video_file() function. This makes it possible for unauthenticated attackers to upload arbitrary files that make remote code execution possible via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
AI Analysis
Technical Summary
CVE-2025-14390 is a vulnerability classified under CWE-434 (Unrestricted Upload of File with Dangerous Type) affecting the Video Merchant plugin for WordPress, specifically versions up to and including 5.0.4. The root cause is the absence or incorrect implementation of nonce validation in the video_merchant_add_video_file() function, which is intended to protect against Cross-Site Request Forgery (CSRF) attacks. Without proper nonce checks, an attacker can craft a malicious request that, when executed by an authenticated administrator (via clicking a link or visiting a crafted webpage), uploads arbitrary files to the server. These files can be crafted to contain malicious code, enabling remote code execution (RCE) on the hosting server. The vulnerability is remotely exploitable without prior authentication but requires user interaction from an admin-level user. The CVSS v3.1 score of 8.8 reflects the ease of exploitation (network vector, low attack complexity), the lack of required privileges, and the high impact on confidentiality, integrity, and availability. Although no public exploits have been reported yet, the vulnerability poses a significant risk to WordPress sites using this plugin, as successful exploitation could lead to full system compromise. The vulnerability was published on December 10, 2025, and no official patches or mitigations have been linked yet, emphasizing the need for proactive defensive measures.
Potential Impact
For European organizations, the impact of this vulnerability can be severe. Successful exploitation could lead to unauthorized access to sensitive data, defacement of websites, deployment of malware, or use of compromised servers as part of botnets or for further attacks. Organizations in sectors such as finance, healthcare, government, and e-commerce that rely on WordPress sites with the Video Merchant plugin are particularly at risk. The compromise of administrative accounts through social engineering or phishing could enable attackers to execute arbitrary code, potentially leading to data breaches, service outages, and reputational damage. Given the widespread use of WordPress across Europe and the popularity of video commerce solutions, the attack surface is significant. Additionally, the GDPR regulatory environment in Europe means that data breaches resulting from exploitation could lead to heavy fines and legal consequences. The lack of known exploits in the wild currently provides a window for mitigation, but the high severity score indicates that organizations should treat this vulnerability as a critical priority.
Mitigation Recommendations
1. Immediately monitor for updates or patches from the Video Merchant plugin developers and apply them as soon as they become available. 2. Until a patch is released, restrict administrative access to trusted IP addresses using firewall rules or VPNs to reduce exposure. 3. Implement Web Application Firewall (WAF) rules to detect and block suspicious file upload attempts and CSRF attack patterns targeting the video_merchant_add_video_file() endpoint. 4. Educate administrators about phishing and social engineering risks, emphasizing caution when clicking on links, especially from untrusted sources. 5. Harden file upload handling by configuring the server to reject executable file types and enforce strict MIME type validation. 6. Regularly audit WordPress plugins and remove or replace those that are no longer maintained or have known vulnerabilities. 7. Enable logging and alerting for unusual file uploads or administrative actions to detect potential exploitation attempts early. 8. Consider deploying Content Security Policy (CSP) headers and other browser-based mitigations to reduce the impact of malicious scripts.
Affected Countries
Germany, France, United Kingdom, Netherlands, Italy, Spain, Poland, Sweden
CVE-2025-14390: CWE-434 Unrestricted Upload of File with Dangerous Type in videomerchant Video Merchant
Description
The Video Merchant plugin for WordPress is vulnerable to Cross-Site Request Forgery in version <= 5.0.4. This is due to missing or incorrect nonce validation on the video_merchant_add_video_file() function. This makes it possible for unauthenticated attackers to upload arbitrary files that make remote code execution possible via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
AI-Powered Analysis
Technical Analysis
CVE-2025-14390 is a vulnerability classified under CWE-434 (Unrestricted Upload of File with Dangerous Type) affecting the Video Merchant plugin for WordPress, specifically versions up to and including 5.0.4. The root cause is the absence or incorrect implementation of nonce validation in the video_merchant_add_video_file() function, which is intended to protect against Cross-Site Request Forgery (CSRF) attacks. Without proper nonce checks, an attacker can craft a malicious request that, when executed by an authenticated administrator (via clicking a link or visiting a crafted webpage), uploads arbitrary files to the server. These files can be crafted to contain malicious code, enabling remote code execution (RCE) on the hosting server. The vulnerability is remotely exploitable without prior authentication but requires user interaction from an admin-level user. The CVSS v3.1 score of 8.8 reflects the ease of exploitation (network vector, low attack complexity), the lack of required privileges, and the high impact on confidentiality, integrity, and availability. Although no public exploits have been reported yet, the vulnerability poses a significant risk to WordPress sites using this plugin, as successful exploitation could lead to full system compromise. The vulnerability was published on December 10, 2025, and no official patches or mitigations have been linked yet, emphasizing the need for proactive defensive measures.
Potential Impact
For European organizations, the impact of this vulnerability can be severe. Successful exploitation could lead to unauthorized access to sensitive data, defacement of websites, deployment of malware, or use of compromised servers as part of botnets or for further attacks. Organizations in sectors such as finance, healthcare, government, and e-commerce that rely on WordPress sites with the Video Merchant plugin are particularly at risk. The compromise of administrative accounts through social engineering or phishing could enable attackers to execute arbitrary code, potentially leading to data breaches, service outages, and reputational damage. Given the widespread use of WordPress across Europe and the popularity of video commerce solutions, the attack surface is significant. Additionally, the GDPR regulatory environment in Europe means that data breaches resulting from exploitation could lead to heavy fines and legal consequences. The lack of known exploits in the wild currently provides a window for mitigation, but the high severity score indicates that organizations should treat this vulnerability as a critical priority.
Mitigation Recommendations
1. Immediately monitor for updates or patches from the Video Merchant plugin developers and apply them as soon as they become available. 2. Until a patch is released, restrict administrative access to trusted IP addresses using firewall rules or VPNs to reduce exposure. 3. Implement Web Application Firewall (WAF) rules to detect and block suspicious file upload attempts and CSRF attack patterns targeting the video_merchant_add_video_file() endpoint. 4. Educate administrators about phishing and social engineering risks, emphasizing caution when clicking on links, especially from untrusted sources. 5. Harden file upload handling by configuring the server to reject executable file types and enforce strict MIME type validation. 6. Regularly audit WordPress plugins and remove or replace those that are no longer maintained or have known vulnerabilities. 7. Enable logging and alerting for unusual file uploads or administrative actions to detect potential exploitation attempts early. 8. Consider deploying Content Security Policy (CSP) headers and other browser-based mitigations to reduce the impact of malicious scripts.
Affected Countries
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2025-12-09T20:50:49.004Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69393d10fd479f45ea600bd0
Added to database: 12/10/2025, 9:27:44 AM
Last enriched: 12/17/2025, 10:35:00 AM
Last updated: 2/4/2026, 8:02:45 PM
Views: 156
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.
Related Threats
CVE-2024-37301: CWE-1336: Improper Neutralization of Special Elements Used in a Template Engine in adfinis document-merge-service
HighCVE-2026-25161: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in AlistGo alist
HighCVE-2026-25160: CWE-295: Improper Certificate Validation in AlistGo alist
CriticalCVE-2026-25145: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in chainguard-dev melange
MediumCVE-2026-25143: CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') in chainguard-dev melange
HighActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.