dbcve.org
Cm Download ManagerWordPress extension · Creative Minds

CVE-2014-8877

HIGH · 10.0 CVSS v2.0 Published 2014-12-05
Fix available
A fix is available. Upgrade to after 2.0.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges 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 alterSearchQuery function in lib/controllers/CmdownloadController.php in the CreativeMinds CM Downloads Manager plugin before 2.0.4 for WordPress allows remote attackers to execute arbitrary PHP code via the CMDsearch parameter to cmdownloads/, which is processed by the PHP create_function function.

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 alterSearchQuery function in lib/controllers/CmdownloadController.php of the CM Downloads Manager WordPress plugin before 2.0.4 uses the PHP create_function with unsanitized user input from the CMDsearch parameter, allowing remote attackers to inject and execute arbitrary PHP code.

MitigationUpdate the CM Downloads Manager plugin to version 2.0.4 or later. The vulnerable create_function call must be replaced with a secure implementation that properly sanitizes and parameterizes search queries.

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.0.3= 2.0.0= 2.0.1= 2.0.2

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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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. Identify if CM Downloads Manager plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'CM Downloads Manager' or 'Creative Minds Cm Download Manager'. Alternatively, check the wp-content/plugins directory for a folder named 'cm-downloads-manager' or similar.
    Affected if The plugin is found in the WordPress installation
  2. Determine the installed plugin version
    In WordPress admin, find the CM Downloads Manager entry in Plugins > Installed Plugins and read the version number displayed beneath the plugin name. Alternatively, open the main plugin file (usually index.php or the primary PHP file in the plugin folder) and look for the 'Version' header in the plugin comments.
    Affected if The version is 2.0.0, 2.0.1, 2.0.2, or any version <= 2.0.3
  3. Locate the vulnerable controller file
    Navigate to the plugin directory in wp-content/plugins and locate the file lib/controllers/CmdownloadController.php. Verify the file exists.
    Affected if The file lib/controllers/CmdownloadController.php exists in the plugin directory
  4. Inspect the alterSearchQuery function for vulnerable code
    Open lib/controllers/CmdownloadController.php and locate the alterSearchQuery function. Search for the use of 'create_function' within that function. The vulnerable pattern will contain create_function with the CMDsearch parameter directly injected.
    Affected if The alterSearchQuery function contains create_function using unsanitized CMDsearch parameter input

A user is affected if the CM Downloads Manager plugin versions 2.0.0 through 2.0.3 are installed and the vulnerable alterSearchQuery function using create_function with the CMDsearch parameter is present.

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
Upgrade available Upgrade to a release after 2.0.3
Interim mitigation

Update the CM Downloads Manager plugin to version 2.0.4 or later. The vulnerable create_function call must be replaced with a secure implementation that properly sanitizes and parameterizes search queries.

Recommended fix High confidence

CM Downloads Manager version 2.0.4 or later

  1. Backup your WordPress site and database before making any changes
  2. Navigate to the WordPress admin dashboard > Plugins section
  3. Locate the CM Downloads Manager plugin
  4. Update the plugin to version 2.0.4 or later
  5. Verify the update was successfully applied by checking the plugin version

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

Fix this in Cm Download Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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