dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-14508

MEDIUM · 6.5 CVSS v3.1 Published 2025-12-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 MediaCommander – Bring Folders to Media, Posts, and Pages plugin for WordPress is vulnerable to unauthorized data deletion due to a missing capability check on the import-csv REST API endpoint in all versions up to, and including, 2.3.1. This is due to the endpoint using `upload_files` capability check (Author level) for a destructive operation that can delete all folders. This makes it possible for authenticated attackers, with Author-level access and above, to delete all folder organization data created by Administrators and other users.

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 MediaCommander WordPress plugin has a REST API endpoint (import-csv) that performs destructive deletion of all folder organization data but only validates for the `upload_files` capability (Author level). This allows any authenticated user with Author-level access or higher to delete all folders created by Administrators and other users, due to a missing capability check on a high-impact operation.

MitigationUpdate the plugin to version 2.3.2 or later which should include proper capability checks. Until then, consider disabling the plugin or restricting REST API access via server-side configuration.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

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

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 MediaCommander plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for MediaCommander, or check /wp-content/plugins/ directory for the mediacommander folder
    Affected if The plugin is installed and active
  2. Check the installed version number
    In WordPress admin Plugins page, click on the plugin name to view details, or read the main plugin file header for version: /wp-content/plugins/mediacommander/mediacommander.php
    Affected if Version is lower than 2.3.2 (the patched version)
  3. Confirm REST API endpoint is accessible
    Send a GET request to /wp-json/mediacommander/v1/import-csv or check if the route is registered by searching the plugin code for 'rest_route' or 'register_rest_route' calls with 'import-csv'
    Affected if The endpoint is registered and responds to requests
  4. Identify users with Author-level or higher access
    In WordPress admin, go to Users > All Users and review the role column. Users with Author, Editor, or Administrator roles have the upload_files capability
    Affected if There are users with Author role or higher who are not intended to have folder deletion access

You are affected if MediaCommander plugin is installed with a version below 2.3.2 and your site has any user with Author-level access or higher.

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

Update the plugin to version 2.3.2 or later which should include proper capability checks. Until then, consider disabling the plugin or restricting REST API access via server-side configuration.

Recommended fix High confidence

Version 2.3.2 or later

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Find the MediaCommander plugin
  4. Click 'Update Now' if an update is available, or manually download version 2.3.2 or higher from wordpress.org/plugins/media-commander/
  5. Verify the update completed successfully
  6. Test that the import-csv endpoint now properly restricts the destructive folder deletion capability

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14508 — 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-14508 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