CVE-2014-9129

CM Download Manager <= 2.0.6 - Cross-Site Request Forgery to Cross-Site Scripting

2014-12-01 00:00
Henri Salo (fgeek)

Strategic Overview

Status
Patched in 2.0.7
Affected Plugin
CM Download Manager – Organize, Protect & Share Files in WordPress
Affected Version
<= 2.0.6
CVSS
6.1Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2014-9129
View all CM Download Manager – Organize, Protect & Share Files in WordPress vulnerabilities

At a glance

CVE-2014-9129 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the CM Download Manager WordPress plugin, affecting versions <= 2.0.6. It carries a CVSS score of 6.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.0.7; sites on affected versions should update now. Disclosed December 2014, reported by Henri Salo (fgeek).

Vulnerability Overview

Cross-site request forgery (CSRF) vulnerability in the CreativeMinds CM Downloads Manager plugin before 2.0.7 for WordPress allows remote attackers to hijack the authentication of administrators for requests that conduct cross-site scripting (XSS) attacks via the addons_title parameter in the CMDM_admin_settings page to wp-admin/admin.php.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in CM Download Manager <= 2.0.6 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For CM Download Manager the fix is 2.0.7: builds <= 2.0.6 are affected, anything from 2.0.7 onward is not.

Remediation

Update to version 2.0.7, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to CM Download Manager: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: CM Download Manager 2.0.7 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2014-9129https://www.wordfence.com/threat-intel/vulnerabilities/id/fabd576c-6990-40a1-9a94-ecb63e2b0189https://nvd.nist.gov/vuln/detail/CVE-2014-9129

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C