Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-14390: CWE-434 Unrestricted Upload of File with Dangerous Type in videomerchant Video Merchant

0
High
VulnerabilityCVE-2025-14390cvecve-2025-14390cwe-434
Published: Wed Dec 10 2025 (12/10/2025, 09:23:56 UTC)
Source: CVE Database V5
Vendor/Project: videomerchant
Product: 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

AILast updated: 12/10/2025, 09:36:11 UTC

Technical Analysis

The vulnerability identified as CVE-2025-14390 affects the Video Merchant plugin for WordPress, specifically versions up to and including 5.0.4. The core issue is a Cross-Site Request Forgery (CSRF) vulnerability stemming from missing or incorrect nonce validation in the function video_merchant_add_video_file(). Nonces in WordPress are security tokens used to verify that requests are intentional and originate from legitimate users. The absence or improper implementation of this validation allows attackers to craft malicious requests that, when executed by an authenticated administrator (via social engineering such as clicking a link), permit the upload of arbitrary files. This unrestricted file upload vulnerability (CWE-434) is particularly dangerous because it can lead to remote code execution (RCE), allowing attackers to execute malicious code on the server hosting the WordPress site. The CVSS 3.1 score of 8.8 reflects the vulnerability's high impact on confidentiality, integrity, and availability, with an attack vector that is network-based, requires no privileges, but does require user interaction. Although no known exploits are currently reported in the wild, the vulnerability's nature and ease of exploitation make it a critical threat. The lack of available patches at the time of reporting increases the urgency for organizations to implement interim protective measures.

Potential Impact

For European organizations, the impact of this vulnerability can be severe. Successful exploitation could lead to full compromise of WordPress sites running the Video Merchant plugin, resulting in unauthorized access to sensitive customer data, defacement of websites, insertion of malware, or use of the compromised server as a pivot point for further attacks within the network. E-commerce platforms and media companies relying on this plugin risk significant financial losses, reputational damage, and regulatory penalties under GDPR if personal data is exposed. The attack requires tricking an administrator, which means social engineering risks are elevated. Given the widespread use of WordPress across Europe, especially in small to medium enterprises, the potential attack surface is large. The availability of the site could also be disrupted, impacting business continuity. The absence of known exploits currently provides a window for proactive defense, but the high CVSS score indicates that once exploited, the consequences would be critical.

Mitigation Recommendations

1. Immediately audit WordPress sites for the presence of the Video Merchant plugin and identify versions in use. 2. Disable or uninstall the Video Merchant plugin until a vendor patch is released. 3. Restrict administrative access to trusted personnel only and enforce multi-factor authentication (MFA) to reduce the risk of compromised admin accounts. 4. 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. 5. Educate administrators about the risks of clicking on unsolicited links and train them to recognize phishing attempts. 6. Monitor server logs and WordPress upload directories for unusual file uploads or modifications. 7. Once a patch is available, apply it promptly and verify nonce validation is correctly implemented. 8. Consider deploying Content Security Policy (CSP) headers to limit the execution of unauthorized scripts. 9. Regularly back up WordPress sites and databases to enable quick recovery in case of compromise. 10. Engage in threat intelligence sharing with industry peers to stay informed about emerging exploits related to this vulnerability.

Need more detailed analysis?Get Pro

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/10/2025, 9:36:11 AM

Last updated: 12/11/2025, 6:41:08 AM

Views: 72

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats