Skip to content
Fencer Vulns
medium 4.8

CVE-2022-34258 json

Adobe Commerce Stored XSS Arbitrary code execution

published 2022-08-16 4 y ago modified 2026-09-10 1 mo ago also BIT-magento-2022-34258 , EUVD-2022-6487 , GHSA-5m55-g8pv-x8ww

cvss
4.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
69.9%
EPSS 69.9% chance of exploitation in 30 days, percentile 99.3%
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 a stored Cross-Site Scripting (XSS) vulnerability that could be abused by an attacker with admin privileges to inject malicious scripts into vulnerable form fields. Malicious JavaScript may be executed in a victim’s browser when they browse to the page containing the vulnerable field.

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

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
18 mo ago

Exploit prediction

69.93% chance of exploitation in the next 30 days, higher than 99.3% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 4.8 CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N
GitHub 3.1 5.5 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N
OSV 3.1 4.8 CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/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
  • CWE-79 Improper Neutralization of Input During Web Page Generation

References

Sources

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.