dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-24956

CRITICAL · 9.3 CVSS v3.1 Published 2026-02-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Shahjada Download Manager Addons for Elementor wpdm-elementor allows Blind SQL Injection.This issue affects Download Manager Addons for Elementor: from n/a through <= 1.3.0.

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 Shahjada Download Manager Addons for Elementor plugin (wpdm-elementor) up to version 1.3.0. The vulnerability stems from improper neutralization of special elements in SQL commands, allowing authenticated or unauthenticated attackers to inject malicious SQL queries through unsanitized input parameters.

MitigationUpdate to a patched version of the plugin once released. Until then, implement Web Application Firewall (WAF) rules to block SQL injection attempts and restrict administrative access to minimize exposure.

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

CVSS:3.1/AV:N/AC:L/PR:N/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 if wpdm-elementor plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Shahjada Download Manager Addons for Elementor' or 'wpdm-elementor' in the installed plugins list, or inspect the plugins directory for the wpdm-elementor folder
    Affected if The plugin is present in the installation
  2. Identify installed plugin version
    In WordPress admin > Plugins, click on the plugin details to view the installed version number, or check the plugin's main PHP file for the Version header in the plugin comment block
    Affected if The installed version is 1.3.0 or lower (any version up to and including 1.3.0)
  3. Verify the plugin is active
    In WordPress admin > Plugins, confirm the plugin status shows as 'Active'
    Affected if The plugin is activated and running on the site
  4. Check if the vulnerable endpoint is accessible
    Test access to the plugin's public-facing functionality that handles input parameters (such as download requests or search parameters), as the SQL injection occurs through unsanitized input parameters in these features
    Affected if The plugin's frontend features are accessible without authentication or with low-privilege user access

If the wpdm-elementor plugin version 1.3.0 or lower is installed and active, the site is vulnerable to SQL injection through unsanitized input parameters in the plugin's functionality.

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 to a patched version of the plugin once released. Until then, implement Web Application Firewall (WAF) rules to block SQL injection attempts and restrict administrative access to minimize exposure.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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