CVE-2021-21025 json
Magento Commerce XML Injection Could Lead To Arbitrary Code Execution
published 2021-02-11 5 y ago modified 2026-09-08 2 mo ago also BIT-magento-2021-21025 , EUVD-2022-4058 , GHSA-h437-qjj9-vmq4
- cvss
- 9.1
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.4%
- EPSS 3.4% chance of exploitation in 30 days, percentile 88%
- 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 vulnerable to XML injection in the product layout updates. Successful exploitation could lead to arbitrary code execution by an authenticated 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
3.41% chance of exploitation in the next 30 days, higher than 88% 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 |
| packagist | magento/project-community-edition | <=2.0.2 |
no fix listed |
| 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-91 XML Injection
References
-
helpx.adobe.com
/security/products/magento/apsb21-08.html
web, vendor-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2021-21025
advisory, web
-
github.com
/magento/magento2
package
Sources
- CVE List CVE-2021-21025
- GitHub Advisory GHSA-h437-qjj9-vmq4
- NVD CVE-2021-21025
- OSV BIT-magento-2021-21025
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.