CVE-2026-4401
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 · uneditedThe 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 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 confidenceThe Download Monitor WordPress plugin is vulnerable to Cross-Site Request Forgery in the actions_handler() and bulk_actions_handler() methods in class-dlm-downloads-path.php. The vulnerability exists in versions up to 5.1.10 due to missing nonce verification, allowing unauthenticated attackers to manipulate download paths (delete, enable, disable) through forged requests that trick authenticated administrators into clicking malicious links.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Locate the WordPress Download Monitor plugin versionNavigate to Plugins > Installed Plugins in the WordPress admin dashboard and find the 'Download Monitor' plugin. The version number is displayed below the plugin name.Affected if The displayed version is 5.1.10 or lower.
-
Verify the vulnerable file existsAccess the WordPress site via file system or FTP and locate the file `/wp-content/plugins/download-monitor/includes/class-dlm-downloads-path.php`. This file contains the vulnerable `actions_handler()` and `bulk_actions_handler()` methods.Affected if The file exists and the plugin version is 5.1.10 or lower.
-
Check for nonce verification in the vulnerable methodsOpen `class-dlm-downloads-path.php` and locate the `actions_handler()` and `bulk_actions_handler()` methods. Search for calls to `wp_verify_nonce()`, `check_admin_referer()`, or similar nonce verification functions within these methods.Affected if No nonce verification is found in either method, and the plugin version is 5.1.10 or lower.
A user is affected if the Download Monitor plugin is installed at version 5.1.10 or earlier and the `actions_handler()` and `bulk_actions_handler()` methods lack nonce verification.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate to version 5.1.11 or later which includes nonce verification. Until patched, administrators should avoid clicking untrusted links while logged in, but patching is the definitive solution.
5.1.11
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate the Download Monitor plugin
- Click 'Update now' if an update is available, or manually update to version 5.1.11 or later
- Verify the update completed successfully
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-4401 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-4401 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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