dbcve.org
Download MonitorWordPress extension · Wpchill

CVE-2022-4972

HIGH · 7.5 CVSS v3.1 Published 2024-10-16
Fix available
A fix is available. Upgrade to after 4.7.51 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 authorization bypass due to a missing capability check on several REST-API routes related to reporting in versions up to, and including, 4.7.51. This makes it possible for unauthenticated attackers to view user data and other sensitive information intended for administrators.

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 versions up to 4.7.51 lacks proper capability checks on multiple REST-API endpoints related to reporting functionality. This allows any unauthenticated user to access sensitive administrative data including user information by directly calling these unprotected API routes.

MitigationUpdate the Download Monitor plugin to version 4.7.52 or later which includes proper authorization checks on the affected REST-API routes. Until patched, consider restricting access to the WordPress REST API via server configuration or a security plugin.

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.7.51

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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Download Monitor' by WPChill, or check the plugins directory via file system at /wp-content/plugins/download-monitor/
    Affected if The Download Monitor plugin is not found in the installation
  2. Check installed version number
    In WordPress admin, find the version number listed on the Plugins page next to Download Monitor, or read the main plugin file /wp-content/plugins/download-monitor/readme.txt and look at the 'Stable tag' or changelog for version 4.7.51
    Affected if Version is 4.7.51 or lower
  3. Confirm REST API accessibility
    Send a GET request to your site's WordPress REST API endpoint: https://yoursite.com/wp-json/ (no authentication headers)
    Affected if The REST API returns a 200 OK response with site information, indicating it accepts unauthenticated requests
  4. Test vulnerable reporting endpoints
    Send unauthenticated GET requests to these potential endpoints: /wp-json/dlm/v1/reports, /wp-json/download-monitor/v1/reports, /wp-json/dlm/reports, or /wp-json/dlm/v1/logs - check each for 200 responses containing user data or download statistics
    Affected if Any of these endpoints return sensitive administrative data or download logs without authentication

You are affected if Download Monitor version 4.7.51 or lower is installed AND the WordPress REST API is accessible to unauthenticated users, as evidenced by vulnerable reporting endpoints returning data without authentication.

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.7.51
Interim mitigation

Update the Download Monitor plugin to version 4.7.52 or later which includes proper authorization checks on the affected REST-API routes. Until patched, consider restricting access to the WordPress REST API via server configuration or a security plugin.

Recommended fix High confidence

Download Monitor version 4.7.52 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Download Monitor' plugin
  4. Click 'Update now' if an update is available, or manually upload version 4.7.52 or later
  5. After updating, verify the REST API endpoints are no longer accessible without authentication by testing the /wp-json/dlm/v1/ routes

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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