CVE-2021-21024 json
Magento Commerce Blind SQL Injection Could Lead To Unauthorized Access
published 2021-02-11 5 y ago modified 2026-09-08 2 mo ago also BIT-magento-2021-21024 , EUVD-2022-5181 , GHSA-rj4f-cp4v-hvcv
- cvss
- 9.1
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.8%
- EPSS 2.8% chance of exploitation in 30 days, percentile 86%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- packagist magento/community-edition 2.3.6-p1, 2.4.1-p1
- bitnami magento 2.3.6, 2.4.1
- magento magento 2.3.6
Exploit prediction
2.81% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 9.1 | CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H |
| GitHub | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H |
| NVD | 2.0 | 6.5 | AV:N/AC:L/Au:S/C:P/I:P/A:P |
| OSV | 3.0 | 9.1 | CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | magento/community-edition | <2.3.6-p1 >=2.4.0, <2.4.1-p1 |
2.3.6-p1 2.4.1-p1 |
| bitnami | magento | <2.3.6 >=2.4.0, <2.4.1 |
2.3.6 2.4.1 |
Affected products
- Adobe Magento Commerce
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
-
helpx.adobe.com
/security/products/magento/apsb21-08.html
web, vendor-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2021-21024
advisory, web
-
github.com
/magento/magento2
package
Sources
- CVE List CVE-2021-21024
- GitHub Advisory GHSA-rj4f-cp4v-hvcv
- NVD CVE-2021-21024
- OSV BIT-magento-2021-21024
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.