dbcve.org
Cm Download ManagerWordPress extension · Cminds

CVE-2020-24146

HIGH · 8.1 CVSS v3.1 Published 2021-07-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
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
Directory traversal in the CM Download Manager (aka cm-download-manager) plugin 2.7.0 for WordPress allows authorized users to delete arbitrary files and possibly cause a denial of service via the fileName parameter in a deletescreenshot action.

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

Directory traversal vulnerability in WordPress CM Download Manager plugin 2.7.0 allows authenticated users to delete arbitrary files via the fileName parameter in the deletescreenshot action. The parameter lacks proper sanitization, enabling path traversal sequences (e.g., ../../../') to access and delete files outside the intended upload directory.

MitigationUpdate to a patched version of CM Download Manager if available; otherwise, restrict or disable the deletescreenshot functionality for untrusted users until proper path validation can be implemented.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Cm Download ManagerWordPress extension
Affected:= 2.7.0

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
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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. Confirm WordPress installation
    Check if WordPress is present by looking for wp-load.php in the web root or checking for WordPress-specific tables in the database.
    Affected if WordPress is installed and running the vulnerable plugin.
  2. Verify CM Download Manager plugin is installed
    Check the wp-content/plugins/ directory for the cm-download-manager folder, or list active plugins via WordPress admin or database query on wp_options table.
    Affected if The CM Download Manager plugin is installed on the WordPress site.
  3. Identify installed plugin version
    Review the main plugin file (e.g., cm-download-manager.php) for the version constant, or check the plugin header comment, or query the WordPress plugins database table for the plugin version metadata.
    Affected if The installed version is exactly 2.7.0.
  4. Determine if authenticated user access exists
    Review WordPress user roles and capabilities, specifically check if any user roles other than Administrator have access to the CM Download Manager plugin backend functions or if the plugin exposes the deletescreenshot action to lower-privilege users.
    Affected if Non-administrator or untrusted user accounts exist with access to the plugin functionality.
  5. Check for deletescreenshot endpoint accessibility
    Inspect plugin code for the deletescreenshot action handler, or test (in a non-production manner) whether the action is reachable via wp-admin/admin-ajax.php or a frontend endpoint, noting that authentication is required but any authenticated user qualifies.
    Affected if The deletescreenshot action is accessible to authenticated users below administrator level.

You are affected if the CM Download Manager plugin version is exactly 2.7.0 AND your WordPress site has authenticated users (particularly non-administrators) who can access the deletescreenshot functionality.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to a patched version of CM Download Manager if available; otherwise, restrict or disable the deletescreenshot functionality for untrusted users until proper path validation can be implemented.

Fix this in Cm Download Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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