Skip to content
Fencer Intel
high 7.5

CVE-2022-34256 json

Adobe Commerce Improper Authorization Privilege escalation

published 4y ago modified last mo. also BIT-magento-2022-34256 , EUVD-2022-6615 , GHSA-r7mm-grf3-5fjv

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
2.2%
EPSS 2.2% chance of exploitation in 30 days, percentile 82%
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 Authorization vulnerability that could result in Privilege escalation. An attacker could leverage this vulnerability to access other user's data. Exploitation of this issue does not require user interaction.

Patch / fix

  • packagist magento/community-edition 2.3.7-p4, 2.4.3-p3, 2.4.5
  • bitnami magento 2.3.7, 2.4.3
  • adobe commerce 2.3.7, 2.4.3
  • magento magento 2.3.7, 2.4.3

Is CVE-2022-34256 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
last yr.

Exploit prediction

2.21% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-09).

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
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OSV 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.3.0, <2.3.7-p4
>=2.4.4, <2.4.5
>=2.4.0, <2.4.3-p3
2.3.7-p4
2.4.5
2.4.3-p3
bitnami magento
>=2.3.0, <2.3.7
>=2.4.0, <2.4.3
>=2.3.7-p1, <=2.3.7-p1
>=2.3.7-p2, <=2.3.7-p2
>=2.3.7-p3, <=2.3.7-p3
>=2.3.7, <=2.3.7
>=2.4.3-p1, <=2.4.3-p1
>=2.4.3-p2, <=2.4.3-p2
>=2.4.3, <=2.4.3
>=2.4.4, <=2.4.4
2.3.7
2.4.3

Affected products

  • Adobe Magento Commerce

Classification

Weakness

References

Sources

Fencer Intel 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.