CVE-2022-35692 json
Adobe Commerce Improper Access Control Security feature bypass
published 2022-08-19 4 y ago modified 2026-06-17 4 mo ago also GHSA-gm4m-9rm8-7rxj , EUVD-2022-38568
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 58%
- public exploits
- 0
- none known
Summary
Adobe Commerce versions 2.4.3-p2 (and earlier), 2.3.7-p3 (and earlier) and 2.4.4 (and earlier) are affected by an Improper Access Control vulnerability that could result in a Security feature bypass. An attacker could leverage this vulnerability to leak minor information of another user's account detials. Exploitation of this issue does not require user interaction.
Patch / fix
- packagist magento/community-edition 2.3.7-p4, 2.4.3-p3
- adobe commerce 2.4.4
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 18 mo ago
Exploit prediction
0.86% chance of exploitation in the next 30 days, higher than 58% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| GitHub | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | magento/community-edition | >=2.4.3-p1, <2.4.3-p3 >=2.3.7-p1, <2.3.7-p4 1 listed version |
2.4.3-p3 2.3.7-p4 |
| packagist | magento/project-community-edition | <=2.0.2 |
no fix listed |
Affected products
- Adobe Magento Commerce
Classification
- Weakness
-
- CWE-863 Incorrect Authorization
References
-
helpx.adobe.com
/security/products/magento/apsb22-38.html
web, patch, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-35692
advisory
Sources
- CVE List CVE-2022-35692
- GitHub Advisory GHSA-gm4m-9rm8-7rxj
- NVD CVE-2022-35692
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.