CVE-2020-24407 json
Arbitrary code execution via file import functionality
published 2020-11-09 5 y ago modified 2026-09-08 2 mo ago also BIT-magento-2020-24407 , EUVD-2022-3044 , GHSA-7pxg-6p87-8c9v
- cvss
- 9.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 5.3%
- EPSS 5.3% chance of exploitation in 30 days, percentile 92%
- public exploits
- 0
- none known
Summary
Magento versions 2.4.0 and 2.3.5p1 (and earlier) are affected by an unsafe file upload vulnerability that could result in arbitrary code execution. This vulnerability could be abused by authenticated users with administrative permissions to the System/Data and Transfer/Import components.
Patch / fix
- packagist magento/community-edition 2.4.1
- bitnami magento 2.3.5, 2.4.1
- magento magento 2.3.5
Exploit prediction
5.27% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.1 | CVSS:3.1/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 | 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 | 9.0 | AV:N/AC:L/Au:S/C:C/I:C/A:C |
| OSV | 3.1 | 9.1 | CVSS:3.1/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.4.1 |
2.4.1 |
| packagist | magento/project-community-edition | <=2.0.2 |
no fix listed |
| bitnami | magento | <2.3.5 >=2.4.0, <2.4.1 |
2.3.5 2.4.1 |
Affected products
- Adobe Magento Commerce
Classification
- Weakness
-
- CWE-434 Unrestricted Upload of File with Dangerous Type
References
-
helpx.adobe.com
/security/products/magento/apsb20-59.html
web, vendor-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-24407
advisory, web
-
github.com
/magento/magento2
package
Sources
- CVE List CVE-2020-24407
- GitHub Advisory GHSA-7pxg-6p87-8c9v
- NVD CVE-2020-24407
- OSV BIT-magento-2020-24407
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.