CVE-2024-1231

CM Download Manager < 2.9.0 - Cross-Site Request Forgery via unpublishHeader

2024-03-25 00:00
Sushmita Poudel

Strategic Overview

Status
Patched in 2.9.0
Affected Plugin
CM Download Manager – Organize, Protect & Share Files in WordPress
Affected Version
< 2.9.0
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2024-1231
View all CM Download Manager – Organize, Protect & Share Files in WordPress vulnerabilities

At a glance

CVE-2024-1231 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the CM Download Manager WordPress plugin, affecting versions < 2.9.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.9.0; sites on affected versions should update now. Disclosed March 2024, reported by Sushmita Poudel.

Vulnerability Overview

The CM Download Manager plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to 2.9.0. This is due to missing or incorrect nonce validation on the 'unpublishHeader' function. This makes it possible for unauthenticated attackers to unpublish downloads via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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)

CM Download Manager < 2.9.0 carries this weakness at unpublishHeader, and reaching it 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.9.0: builds < 2.9.0 are affected, anything from 2.9.0 onward is not.

Remediation

Update to version 2.9.0, 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.9.0 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-1231https://www.wordfence.com/threat-intel/vulnerabilities/id/f6a0d6df-60a6-42e3-9e9b-6171bb589f4ehttps://nvd.nist.gov/vuln/detail/CVE-2024-1231

Related records

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