dbcve.org
Improper AuthorizationWeakness · CWE-285

CVE-2024-3269

MEDIUM · 5.4 CVSS v3.1 Published 2024-05-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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 Download Monitor plugin for WordPress is vulnerable to unauthorized access to functionality due to a missing capability check on the dlm_uninstall_plugin function in all versions up to, and including, 4.9.13. This makes it possible for authenticated attackers to uninstall the plugin and delete its data.

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 Download Monitor WordPress plugin has a broken access control vulnerability where the dlm_uninstall_plugin function lacks a capability check. This allows any authenticated user (even with low privileges like subscriber) to trigger plugin uninstallation and data deletion by calling this function directly.

MitigationUpdate the Download Monitor plugin to version 4.9.14 or later which includes the missing capability check. If immediate update is not possible, consider restricting access to the uninstall functionality via web server rules or temporarily disabling the plugin.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if Download Monitor plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Download Monitor' in the list, or check the /wp-content/plugins/download-monitor/ directory exists on the server
    Affected if Plugin is installed and active
  2. Identify the installed version of Download Monitor
    In WordPress admin, go to Plugins > Installed Plugins and click on the plugin to view version details, or read the version header from the main plugin file at /wp-content/plugins/download-monitor/download-monitor.php
    Affected if Version number is below 4.9.14
  3. Verify the vulnerability condition
    Compare your installed version to the affected range: any version prior to 4.9.14 contains the missing capability check in the dlm_uninstall_plugin function
    Affected if Installed version is 4.9.13 or earlier

You are affected if the Download Monitor plugin is installed with any version prior to 4.9.14, as these versions lack the capability check that prevents low-privileged authenticated users from triggering plugin uninstallation.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Download Monitor plugin to version 4.9.14 or later which includes the missing capability check. If immediate update is not possible, consider restricting access to the uninstall functionality via web server rules or temporarily disabling the plugin.

Recommended fix Moderate confidence

4.9.14 or latest available version

  1. Update the Download Monitor plugin to the latest version available in the WordPress plugin repository
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate Download Monitor and click 'Update Now' if an update is available
  4. After updating, verify the plugin is functioning correctly

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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