CVE-2026-4401

Download Monitor <= 5.1.10 - Cross-Site Request Forgery to Download Path Deletion and Disabling

2026-04-07 11:17
alex_henry20

Strategic Overview

Status
Patched in 5.1.11
Affected Plugin
Download Monitor
Affected Version
<= 5.1.10
CVSS
5.4Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2026-4401
View all Download Monitor vulnerabilities

At a glance

CVE-2026-4401 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Download Monitor WordPress plugin, affecting versions <= 5.1.10. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 5.1.11; sites on affected versions should update now. Disclosed April 2026, reported by alex_henry20.

Vulnerability Overview

The Download Monitor plugin for WordPress is vulnerable to Cross-Site Request Forgery in the `actions_handler()` and `bulk_actions_handler()` methods in `class-dlm-downloads-path.php` in all versions up to, and including, 5.1.10. This is due to missing nonce verification on these functions. This makes it possible for unauthenticated attackers to delete, disable, or enable approved download paths 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)

Download Monitor <= 5.1.10 carries this weakness at actions_handler(), 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 Download Monitor the fix is 5.1.11: builds <= 5.1.10 are affected, anything from 5.1.11 onward is not.

Remediation

Update to version 5.1.11, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

Related records

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