CVE-2023-38220 json
Full page cache enumeration via cookie X-Magento-Vary
published 2023-10-13 3 y ago modified 2026-06-17 4 mo ago also GHSA-grc6-r6f8-xj7c , EUVD-2023-42040
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 56%
- public exploits
- 0
- none known
Summary
Adobe Commerce versions 2.4.7-beta1 (and earlier), 2.4.6-p2 (and earlier), 2.4.5-p4 (and earlier) and 2.4.4-p5 (and earlier) are affected by an Improper Authorization vulnerability that could lead in a security feature bypass in a way that an attacker could access unauthorised data. Exploitation of this issue does not require user interaction.
Patch / fix
- packagist magento/community-edition 2.4.4-p6, 2.4.5-p5, 2.4.6-p3, 2.4.7-beta2
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 20 mo ago
Exploit prediction
0.80% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | magento/community-edition | >=2.4.7-beta1, <2.4.7-beta2 1 listed version >=2.4.6-p1, <2.4.6-p3 >=2.4.5-p1, <2.4.5-p5 >=2.4.4-p1, <2.4.4-p6 |
2.4.7-beta2 2.4.6-p3 2.4.5-p5 2.4.4-p6 |
| packagist | magento/project-community-edition | <=2.0.2 |
no fix listed |
Affected products
- Adobe Adobe Commerce
Classification
- Weakness
-
- CWE-285 Improper Authorization
References
-
helpx.adobe.com
/security/products/magento/apsb23-50.html
vendor-advisory, web
-
nvd.nist.gov
/vuln/detail/CVE-2023-38220
advisory
-
github.com
/magento/magento2
package
Sources
- CVE List CVE-2023-38220
- GitHub Advisory GHSA-grc6-r6f8-xj7c
- NVD CVE-2023-38220
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.