dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-39486

HIGH · 8.5 CVSS v3.1 Published 2026-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in WP Chill Download Monitor download-monitor allows Blind SQL Injection.This issue affects Download Monitor: from n/a through <= 5.1.8.

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

SQL Injection vulnerability in the WordPress Download Monitor plugin allows attackers to inject malicious SQL queries via unsanitized user input. This is a blind SQL injection, meaning attackers infer database contents through true/false conditions or timing differences rather than seeing direct output.

MitigationUpdate Download Monitor plugin to the latest patched version. If no patched version is available, implement input validation/sanitization on all user-supplied parameters and consider deploying a WAF rule to block SQL injection attempts until a fix is released.

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
Changed
Confidentiality
High
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/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 the installed Download Monitor plugin version
    Navigate to WordPress admin > Plugins > Installed Plugins, locate 'Download Monitor' (by WP Chill), and note the version number displayed. Alternatively, inspect the plugin's main PHP file or readme.txt in wp-content/plugins/download-monitor/ for the 'Version:' header.
    Affected if The displayed version is 5.1.8 or lower (any version up to and including 5.1.8).
  2. Verify the plugin is active and publicly accessible
    Confirm the Download Monitor plugin status is 'Active' in the WordPress plugins list. Since this is an unauthenticated vulnerability, the plugin need only be active - no specific user role is required for exploitation.
    Affected if The plugin is active and the WordPress site is publicly accessible to unauthenticated users.
  3. Identify which plugin endpoints handle user input
    Review the Download Monitor plugin files (particularly the handler/hook files) to locate functions processing request parameters without sanitization. Common WordPress SQL injection entry points include query parameters in URLs (e.g., ?dl_id= or similar) used by the plugin's download tracking or file serving logic.
    Affected if The plugin is processing GET or POST request parameters directly in SQL queries without using $wpdb->prepare() or equivalent sanitization functions.
  4. Inspect web server access logs for SQL injection patterns
    Search access logs (typically in /var/log/apache2/access.log or similar location) for requests to the WordPress site containing SQL keywords (SELECT, UNION, INSERT, --, /*, OR 1=1) in query parameters. Focus on URLs containing 'download-monitor', 'dl', or 'download' in the path.
    Affected if Logs contain suspicious requests with SQL syntax in parameters targeting the Download Monitor plugin's endpoints, especially from unauthenticated (no auth cookie/token) sources.

A user is affected if the Download Monitor plugin version is 5.1.8 or lower, the plugin is active, and the site is accessible to unauthenticated users - particularly if suspicious SQL-like patterns appear in access logs.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Download Monitor plugin to the latest patched version. If no patched version is available, implement input validation/sanitization on all user-supplied parameters and consider deploying a WAF rule to block SQL injection attempts until a fix is released.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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