dbcve.org
MagentoCMS

CVE-2021-21024

CRITICAL · 9.1 CVSS v3.0 Published 2021-02-11
Fix available
A fix is available. Upgrade to 2.3.6 or later.
See remediation →
97/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
Magento versions 2.4.1 (and earlier), 2.4.0-p1 (and earlier) and 2.3.6 (and earlier) are affected by a blind SQL injection vulnerability in the Search module. Successful exploitation could lead to unauthorized access to restricted resources by an unauthenticated attacker. Access to the admin console is required for successful exploitation.

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

Blind SQL injection vulnerability in Magento 2's Search module affecting versions 2.4.1 and earlier, 2.4.0-p1 and earlier, and 2.3.6 and earlier. The vulnerability allows unauthenticated attackers to inject malicious SQL queries through the search functionality, potentially granting unauthorized access to restricted database resources.

MitigationApply the official Adobe Magento security patch or upgrade to a patched version (2.4.2 or later). Restrict admin console access to trusted personnel only as a defense-in-depth measure.

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
MagentoCMS
Affected:< 2.3.6= 2.3.6= 2.4.0= 2.4.1

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
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Magento version
    Run 'bin/magento --version' from the Magento root directory, or inspect the 'version' field in composer.lock, or check the footer of the admin dashboard page which displays the Magento version.
    Affected if The installed version is 2.3.6, 2.4.0, 2.4.1, or any version earlier than these (e.g., 2.4.0-p1). Versions 2.4.2 and later are NOT affected.
  2. Confirm CatalogSearch module is enabled
    Run 'bin/magento module:status Magento_CatalogSearch' from the CLI, or navigate to Stores > Configuration > Catalog > Catalog Search in the admin panel to verify the search module is active.
    Affected if The module is shown as enabled. The vulnerability exists in this module, so it must be enabled for the flaw to be exploitable.
  3. Verify search functionality is publicly accessible
    Attempt a GET request to the frontend search endpoint (typically /catalogsearch/result/?q=test) without authentication. Also check that the search indexer is running via 'bin/magento indexer:status'.
    Affected if The search page loads without requiring authentication. An unauthenticated attacker needs access to the search functionality to exploit this SQL injection.

You are affected if your Magento version is 2.3.6, 2.4.0, 2.4.1, or any earlier version AND the CatalogSearch module is enabled and accessible to unauthenticated users.

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 2.3.6 or later
Fixed in 2.3.6
Interim mitigation

Apply the official Adobe Magento security patch or upgrade to a patched version (2.4.2 or later). Restrict admin console access to trusted personnel only as a defense-in-depth measure.

Recommended fix High confidence

Magento 2.3.7+ (for 2.3.x line) or Magento 2.4.2+ (for 2.4.x line)

  1. 1. Backup your Magento database and filesystem before proceeding.
  2. 2. For Magento 2.3.x deployments: Upgrade to Magento 2.3.7 or later by running: composer require magento/product-community-edition=2.3.7 --no-update followed by composer update.
  3. 3. For Magento 2.4.x deployments: Upgrade to Magento 2.4.2 or later by running: composer require magento/product-community-edition=2.4.2 --no-update followed by composer update.
  4. 4. Clear the Magento cache after upgrade: bin/magento cache:flush.
  5. 5. Reindex all search indexes: bin/magento indexer:reindex.
  6. 6. Verify the upgrade by checking the admin panel and confirming version number under System > Web Setup Wizard > Version.
Caveat Major upgrades between minor versions (e.g., 2.3 to 2.4) may introduce breaking changes to custom code, themes, or third-party extensions; review Magento migration guides

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

Fix this in Magento Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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