dbcve.org
Download MonitorWordPress extension · Wpchill

CVE-2023-34007

HIGH · 8.8 CVSS v3.1 Published 2023-12-20
Fix available
A fix is available. Upgrade to after 4.8.3 or later.
See remediation →
94/100
Remediation priority · Urgent
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
Unrestricted Upload of File with Dangerous Type vulnerability in WPChill Download Monitor.This issue affects Download Monitor: from n/a through 4.8.3.

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 · moderate confidence

Unrestricted file upload vulnerability in the WordPress Download Monitor plugin allows attackers to upload dangerous file types (e.g., executable scripts) without proper validation, potentially enabling remote code execution on the affected WordPress site.

MitigationUpdate Download Monitor to the latest patched version immediately; if an update is unavailable, disable the plugin, implement server-side file type and content validation for uploads, and restrict upload functionality to authenticated administrators only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Download MonitorWordPress extension
Affected:<= 4.8.3

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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. Verify Download Monitor plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'Download Monitor' by Wpchill in the plugin list. Note whether it is activated.
    Affected if Download Monitor plugin is present and activated in WordPress
  2. Confirm installed version is vulnerable
    In the Plugins list, click 'View Details' on Download Monitor to reveal the version number, or inspect the main plugin PHP file for the 'Version' header. Compare the version against <= 4.8.3.
    Affected if Installed version is 4.8.3 or lower
  3. Inspect file upload settings and functionality
    Navigate to Downloads > Add New in the WordPress admin panel. Attempt to add a new download and observe if a file upload interface is present. Check the plugin settings page for any file type restrictions or validation controls.
    Affected if File upload feature is enabled and accessible without proper file type validation controls visible
  4. Examine upload directory for suspicious files
    Access the server file system and review the WordPress uploads folder (typically wp-content/uploads/dlm_uploads or the configured download path). List all files and note any with executable extensions such as .php, .phtml, .js, .sh, .exe, or .cgi.
    Affected if Executable or script-based files are present in the download upload directory
  5. Review user role permissions for uploads
    Check WordPress user roles and permissions settings within Download Monitor. Determine which user roles (Administrator, Editor, Author, Contributor) have the ability to upload files via the plugin.
    Affected if Non-administrator users (Authors, Contributors, or Editors) have permission to upload files through the plugin

Environment is affected if Download Monitor plugin version 4.8.3 or lower is installed with file upload functionality enabled and accessible to users.

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
Upgrade available Upgrade to a release after 4.8.3
Interim mitigation

Update Download Monitor to the latest patched version immediately; if an update is unavailable, disable the plugin, implement server-side file type and content validation for uploads, and restrict upload functionality to authenticated administrators only.

Recommended fix Moderate confidence

Download Monitor 4.8.4 or later (latest available version)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find Download Monitor in the plugin list
  4. Check if an update is available for Download Monitor
  5. If an update is available, click 'Update Now' to install the latest version
  6. Alternatively, download the latest version from the WordPress plugin repository and upload it manually
  7. After updating, verify the plugin is running on a version higher than 4.8.3

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

Fix this in Download Monitor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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