Download MonitorWordPress extension · Wpchill
CVE-2024-30501
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 · uneditedImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in WPChill Download Monitor.This issue affects Download Monitor: from n/a through 4.9.4.
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 confidenceSQL injection vulnerability in WordPress Download Monitor plugin allows authenticated attackers with low privileges to inject malicious SQL queries through unsanitized input parameters in the 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
< 4.9.5CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Download Monitor plugin is installedLog in to WordPress admin panel, navigate to Plugins > Installed Plugins, and look for 'Download Monitor' or 'Wpchill Download Monitor' in the list of active plugins.Affected if Plugin is installed and active
-
Check installed plugin versionIn the Plugins list, click on 'View Details' next to Download Monitor, or check the plugin header in wp-content/plugins/download-monitor/readme.txt for the version number.Affected if Version is lower than 4.9.5 (e.g., 4.9.4, 4.9.3, etc.)
-
Confirm WordPress user roles existNavigate to Users > All Users in WordPress admin to see if any user accounts exist with Subscriber, Contributor, or Author roles.Affected if At least one low-privilege user account exists on the site
-
Verify plugin functionality is accessibleCheck if the Download Monitor plugin's public-facing features (e.g., download links, shortcodes) are accessible on the site without admin authentication.Affected if Public download functionality is accessible to unauthenticated or low-privileged users
A site is affected if Download Monitor plugin is installed with a version below 4.9.5 and the plugin is active, regardless of whether low-privilege user accounts actually exist.
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 · scoped4.9.5
Update Download Monitor to the latest patched version when available; until then, restrict plugin access to trusted users only and implement WAF rules to detect SQL injection attempts.
Download Monitor version 4.9.5
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate 'Download Monitor' in the plugin list
- If the current version is below 4.9.5, click 'Update Now' to upgrade to the latest version
- After update, verify the running version is 4.9.5 or higher
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 / 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-2024-30501 — 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-2024-30501 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