Video Merchant CVE-2025-14390
HIGHAttack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessTrick admin into clicking link
-
DeliveryDeliver forged cross-site request
-
ExploitBypass missing nonce check
-
ExecutionUpload malicious PHP file
-
PersistAccess webshell for RCE
-
ImpactFull site compromise
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. |
| Exploitation Conditions | Exploitation requires that the site runs the Video Merchant plugin at version 5.0.4 or earlier, where the video_merchant_add_video_file() function lacks correct nonce validation. The attacker does not need credentials (PR:N), but exploitation is strictly gated on tricking an authenticated site administrator into performing an action such as clicking an attacker-supplied link while logged in (UI:R) - without this victim interaction the forged request cannot be submitted. The achievable impact (arbitrary file upload leading to RCE) further depends on the server executing uploaded file types (e.g., PHP) from the upload location. The admin-interaction requirement and the plugin's limited deployment are the primary factors limiting real-world exploitation. |
| Impact | This is a genuinely serious flaw (CVSS 8.8) but its real-world risk is materially lower than the base score suggests because exploitation is not fully self-contained. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H shows network reach, low complexity, and no attacker authentication (PR:N), but crucially requires user interaction (UI:R) - a logged-in site administrator must be tricked into triggering the forged request, which is the defining characteristic of CSRF (CWE-434 file upload chained via missing nonce validation). The EPSS score of 0.45% (37th percentile) is low, indicating no significant observed or predicted mass-exploitation activity. There is NO CISA KEV listing and NO public exploit code flagged in the provided data, so per precision rules this is 'no public exploit identified at time of analysis.' The signals are internally consistent rather than conflicting: a high technical-impact bug (full C/I/A compromise via RCE) gated behind a social-engineering prerequisite and a niche plugin footprint. Conclusion: this is a real patch-worthy issue for sites running Video Merchant, but it is NOT a drop-everything emergency on the level of an unauthenticated, no-interaction RCE - the admin-interaction requirement and low EPSS argue for prioritized-but-not-critical scheduling. |
| Exploit ScenarioDerived | An attacker crafts a malicious web page or email link containing a forged request targeting the vulnerable video_merchant_add_video_file() endpoint and lures a logged-in WordPress administrator into clicking it. Because nonce validation is missing, the victim's browser submits the forged file upload, placing an attacker-controlled executable file (e.g., a PHP webshell) on the server, which the attacker then accesses to achieve remote code execution. No public exploit code is identified at time of analysis, so a working PoC would need to be developed. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Cross-site request forgery in the Video Merchant WordPress plugin through version 5.0.4 lets an attacker upload arbitrary files and reach remote code execution on a victim site by tricking a logged-in administrator into clicking a crafted link. The missing nonce check on video_merchant_add_video_file() is what allows the forged upload request to be accepted without the administrator's intent, and whether code actually runs depends on the server executing the uploaded file type. No public exploit identified at time of analysis and no indication of confirmed active exploitation; EPSS is low at 0.45% (roughly the 37th percentile), so real-world risk is dominated by the required administrator interaction, the plugin's limited deployment, and server-side file-execution behavior rather than by the 8.8 base score alone.
RemediationAI
No vendor-released patch identified at time of analysis: the supplied intelligence lists no fixed version, only the vulnerable range <= 5.0.4, so administrators should check https://wordpress.org/plugins/video-merchant and the Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/7cbe39ae-d10b-432f-afab-682948de2521?source=cve for the current plugin release before upgrading, and should treat any version newer than 5.0.4 cautiously until a fix is confirmed. The most reliable action is to deactivate and delete the plugin if it is not essential, which removes the vulnerable endpoint entirely; if it must stay, restrict who can reach the site's admin area and treat update guidance as critical. Because the exploit requires an administrator to click an attacker-supplied link while authenticated, practical mitigation includes hardening admin browsing habits and, where feasible, deploying a WAF rule that blocks forged upload requests to the plugin's endpoints, though WAF coverage is best-effort and can be bypassed. The single most effective break in the RCE chain is server-side: prevent execution of uploaded file types in wp-content/uploads (for Apache, a 'php_flag engine off' or equivalent per-directory rule; for nginx, a location block denying PHP handling under the uploads path), which stops code execution even if a malicious file lands, at the cost of potentially breaking any legitimate feature that relies on serving executable content from that directory. Enforcing strict MIME and extension allow-listing on uploads adds defence in depth but does not remove the missing-nonce root cause, which can only be corrected by a plugin update.
Affected ProductsAI
All versions of the Video Merchant plugin for WordPress up to and including 5.0.4 (the vulnerable range stated by the source), with the flaw located in the video_merchant_add_video_file() function. The product is the WordPress plugin published at https://wordpress.org/plugins/video-merchant, and the vulnerability is tracked by Wordfence under advisory ID 7cbe39ae-d10b-432f-afab-682948de2521 (https://www.wordfence.com/threat-intel/vulnerabilities/id/7cbe39ae-d10b-432f-afab-682948de2521?source=cve), with the CVE also linked to the plugin repository page. No explicit CPE identifiers were provided in the intelligence feed, so any environment inventory should match on the plugin slug 'video-merchant' and on the installed version being 5.0.4 or lower. Sites that do not have the plugin installed are not affected.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The affected component is the WordPress plugin distributed under the slug 'video-merchant' (Video Merchant), whose upload handler video_merchant_add_video_file() in versions <= 5.0.4 fails to perform correct nonce validation. WordPress relies on nonces verified through functions such as wp_verify_nonce() and check_admin_referer() to bind state-changing requests to the user who initiated them; when that check is absent or wrong on a file-upload action, any third-party page can make a victim's authenticated browser submit the request automatically, which is the classic CWE-352 CSRF pattern. The supplied CWE, however, is CWE-434 (Unrestricted Upload of File with Dangerous Type), reflecting that the forged request carries an attacker-chosen file and that no dangerous-type filtering stops it. Chaining CSRF with an unrestricted upload handler turns a simple state change into arbitrary code execution once the server serves or interprets the uploaded type, typically PHP from a web-accessible uploads directory. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H confirms network reachability, no attacker credentials, and a mandatory victim interaction, with high confidentiality, integrity, and availability impact after exploitation. No CPE strings were included in the supplied intelligence; the package identity is taken from the referenced WordPress plugin directory entry at https://wordpress.org/plugins/video-merchant.
Know when Wordpress Plugin 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
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Unauthenticated remote CSRF (AV:N/PR:N/AC:L) that must trick a logged-in admin (UI:R); arbitrary file upload yields RCE, giving full C/I/A impact.
Primary rating from Vendor (wordfence).
CVSS VectorVendor: wordfence
DescriptionCVE.org
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.
Executive ViewAI
A high-severity flaw in the Video Merchant WordPress plugin (through version 5.0.4) allows an attacker to upload arbitrary files and potentially achieve remote code execution on any site running the plugin, provided a logged-in administrator can be induced to click a crafted link. Because successful exploitation yields code execution on the web server, a single compromised site could expose customer data, deface content, or serve as a pivot into adjacent internal systems. Leadership should weigh the severity against the mitigating factors: a vendor patch is not yet available, no public exploit code has been identified, and real-world exposure depends on administrator interaction and server-side handling of uploaded file types.
No vendor-released patch identified at time of analysis. Interim mitigations: deactivate or remove the Video Merchant plugin (versions 5.0.4 and earlier), enforce multi-factor authentication and least-privilege on WordPress administrator accounts, deploy WAF or reverse-proxy rules to block cross-site forged requests to the plugin's file-upload endpoints, and confirm the web server does not execute uploaded file types in plugin upload directories. Monitor file-integrity and web server logs for unexpected executable files in upload paths.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Request Forgery exploits the automatic credential inclusion behavior of web browsers.
Malicious file upload attacks exploit insufficient validation when web applications accept user-provided files.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB