dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-24663

HIGH · 7.6 CVSS v3.1 Published 2025-01-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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 mra13 Simple Download Monitor simple-download-monitor allows Blind SQL Injection.This issue affects Simple Download Monitor: from n/a through <= 3.9.25.

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

A blind SQL injection vulnerability exists in the Simple Download Monitor WordPress plugin (versions through 3.9.25) due to improper neutralization of special elements in SQL commands. An unauthenticated attacker can inject malicious SQL queries through vulnerable parameters, potentially extracting sensitive data from the database by observing application behavior differences rather than direct output.

MitigationUpdate Simple Download Monitor plugin to the latest version beyond 3.9.25 as soon as a patched release is available; if no update exists, implement strict input validation and convert all database queries to use parameterized statements or prepared queries.

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

CVSS:3.1/AV:N/AC:L/PR:H/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. Confirm Simple Download Monitor plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Simple Download Monitor' in the list. Note whether it is active or inactive.
    Affected if The plugin is installed and active on the WordPress site
  2. Check the installed plugin version
    In the Plugins list, click on the plugin name or view its details to see the version number displayed. Compare this version to the affected range (versions through 3.9.25).
    Affected if The installed version is 3.9.25 or any earlier version of Simple Download Monitor
  3. Identify accessible query parameters
    Review the site's publicly accessible URLs that involve the Simple Download Monitor plugin (download links, shortcode outputs, or API endpoints). Examine which GET or POST parameters are passed that could interact with database queries.
    Affected if The plugin exposes parameters that accept user input without proper sanitization for SQL queries
  4. Review access logs for SQL injection patterns
    Examine web server access logs (Apache, Nginx) for requests to the WordPress site containing SQL syntax in query parameters, such as UNION, SELECT, OR 1=1, or time-based delay functions like SLEEP or WAIT.
    Affected if Log entries show SQL injection payloads targeting Simple Download Monitor parameters

A site is affected if Simple Download Monitor plugin version 3.9.25 or earlier is installed and active, with publicly accessible parameters that can be manipulated for SQL injection.

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 Simple Download Monitor plugin to the latest version beyond 3.9.25 as soon as a patched release is available; if no update exists, implement strict input validation and convert all database queries to use parameterized statements or prepared queries.

Recommended fix Moderate confidence

Simple Download Monitor version 3.9.26 or latest available version

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Find 'Simple Download Monitor' in the plugin list
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest patched version
  5. 5. Alternatively, navigate to Plugins > Add New > Upload and upload the latest version of the plugin from the WordPress plugin repository
  6. 6. After updating, verify the plugin is running version 3.9.26 or higher

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

Have this fixed 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 help mitigating

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-2025-24663 — 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-2025-24663 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