Skip to content
Fencer Vulns
high 8.7

CVE-2025-49557 json

Adobe Commerce | Cross-site Scripting (Stored XSS) (CWE-79)

published 2025-08-12 14 mo ago modified 2026-06-17 4 mo ago also GHSA-8mq8-c243-2335 , EUVD-2025-24448

cvss
8.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 53%
public exploits
0
none known

Summary

Adobe Commerce versions 2.4.9-alpha1, 2.4.8-p1, 2.4.7-p6, 2.4.6-p11, 2.4.5-p13, 2.4.4-p14 and earlier are affected by a stored Cross-Site Scripting (XSS) vulnerability that could be exploited by a low-privileged attacker to inject malicious scripts into vulnerable form fields. A successful attacker can abuse this to achieve session takeover, increasing the confidentiality and integrity impact as high. Exploitation of this issue requires user interaction in that a victim must browse to the page containing the vulnerable field. Scope is changed.

Patch / fix

  • packagist magento/community-edition 2.4.4-p15, 2.4.5-p14, 2.4.6-p12, 2.4.7-p7
  • adobe commerce 2.4.4
  • adobe commerce_b2b 1.3.3
  • adobe magento 2.4.5

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
14 mo ago

Exploit prediction

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

CVSS scores

assigned by version score vector
CNA 3.1 8.7 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N
NVD 3.1 8.7 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N
GitHub 3.1 8.7 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
packagist magento/community-edition
<2.4.4-p15
>=2.4.5-p1, <2.4.5-p14
>=2.4.6-p1, <2.4.6-p12
>=2.4.7-p1, <2.4.7-p7
1 listed version
2.4.4-p15
2.4.5-p14
2.4.6-p12
2.4.7-p7
packagist magento/project-community-edition
<=2.0.2
no fix listed

Affected products

  • Adobe Adobe 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.