CVE-2020-9689 json
Magento path traversal vulnerability
published 2020-07-29 6 y ago modified 2026-09-08 2 mo ago also BIT-magento-2020-9689 , EUVD-2022-3824 , GHSA-fr6f-xmfx-rrpq
- cvss
- 6.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.1%
- EPSS 4.1% chance of exploitation in 30 days, percentile 90%
- public exploits
- 0
- none known
Summary
Magento versions 2.3.5-p1 and earlier, and 2.3.5-p1 and earlier have a path traversal vulnerability. Successful exploitation could lead to arbitrary code execution.
Patch / fix
- packagist magento/community-edition 2.3.5-p2
- bitnami magento 2.3.6
- magento magento 2.3.5
Exploit prediction
4.14% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| GitHub | 3.1 | 6.5 | CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 8.5 | AV:N/AC:M/Au:S/C:C/I:C/A:C |
| OSV | 3.1 | 6.5 | CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | magento/community-edition | <2.3.5-p2 |
2.3.5-p2 |
| packagist | magento/project-community-edition | <=2.0.2 |
no fix listed |
| bitnami | magento | <2.3.6 |
2.3.6 |
Affected products
- Adobe Magento
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
helpx.adobe.com
/security/products/magento/apsb20-47.html
web, patch, vendor-advisory, advisory
-
github.com
/magento/magento2/commit/9436781734e47c83e96977fa770d255217680d5e#diff-7c7399d1d47cdaf120a1a503b7ad87f496d9879
web
-
nvd.nist.gov
/vuln/detail/CVE-2020-9689
advisory, web
-
github.com
/magento/magento2
package
Sources
- CVE List CVE-2020-9689
- GitHub Advisory GHSA-fr6f-xmfx-rrpq
- NVD CVE-2020-9689
- OSV BIT-magento-2020-9689
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.