dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-14390

HIGH · 8.8 CVSS v3.1 Published 2025-12-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Video Merchant WordPress plugin <= 5.0.4 lacks CSRF protection on the video_merchant_add_video_file() function due to missing or incorrect nonce validation. This allows unauthenticated attackers to forge requests by tricking administrators into clicking malicious links, enabling upload of arbitrary files and potential remote code execution.

MitigationImplement proper nonce validation on the video_merchant_add_video_file() function and ensure all state-changing admin actions include valid CSRF tokens. Consider adding file type validation and sanitization for uploaded files.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Video Merchant plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Video Merchant' in the list. Note the installed version displayed.
    Affected if The Video Merchant plugin appears in the installed plugins list with a version number of 5.0.4 or lower.
  2. Check installed plugin version against affected range
    Locate the version number shown in the plugins list for Video Merchant. Compare it to the affected range: any version 5.0.4 or earlier is within the vulnerable range.
    Affected if The installed version is 5.0.4 or any earlier version number.
  3. Inspect the vulnerable function for nonce validation
    Access the plugin files via FTP or file manager. Navigate to the plugin directory and open the file containing video_merchant_add_video_file(). Look for the function definition and check whether it includes a nonce verification call (such as wp_verify_nonce, check_admin_referer, or defined('NONCE_KEY')).
    Affected if The video_merchant_add_video_file() function exists and contains no nonce validation checks, or the nonce check is present but implemented incorrectly.
  4. Verify if the upload functionality is accessible
    Check if the WordPress admin area allows access to video upload features. Test whether the video_merchant_add_video_file() function can be triggered via an admin action hook (such as admin_post, admin_init, or a similar WordPress admin hook).
    Affected if The upload function is hooked to an admin action without CSRF protection, allowing forged requests to succeed when an authenticated admin triggers the request.

If the Video Merchant plugin version is 5.0.4 or earlier and the video_merchant_add_video_file() function lacks proper nonce validation, the environment is affected by this CSRF vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper nonce validation on the video_merchant_add_video_file() function and ensure all state-changing admin actions include valid CSRF tokens. Consider adding file type validation and sanitization for uploaded files.

Recommended fix Moderate confidence

Video Merchant version 5.0.5 or later

  1. Check the current version of the Video Merchant plugin installed on your WordPress site
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. If the installed version is 5.0.4 or lower, navigate to Dashboard > Updates and update the Video Merchant plugin
  4. Alternatively, go to Plugins > Add New > Upload Plugin and upload the latest version from wordpress.org
  5. After updating, verify the new version is 5.0.5 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14390 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-14390 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data