Skip to content
Fencer Vulns
high 8.1

CVE-2025-54264 json

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

published 2025-10-14 12 mo ago modified 2026-10-08 32 d ago also GHSA-2768-5wmv-cfff , EUVD-2025-34464

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

Summary

Adobe Commerce versions 2.4.9-alpha2, 2.4.8-p2, 2.4.7-p7, 2.4.6-p12, 2.4.5-p14, 2.4.4-p15 and earlier are affected by a stored Cross-Site Scripting (XSS) Cross-Site Scripting (XSS) vulnerability that could be abused by a high-privileged attacker 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. A successful attacker can abuse this to achieve session takeover, increasing the confidentiality, and integrity impact to 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.6-p13, 2.4.7-p8, 2.4.8-p3, 2.4.9-alpha3

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
12 mo ago

Exploit prediction

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

CVSS scores

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

Affected packages

ecosystem package affected fixed in
packagist magento/project-community-edition
<=2.0.2
no fix listed
packagist magento/community-edition
>=2.4.9-alpha1, <2.4.9-alpha3
>=2.4.8-beta1, <2.4.8-p3
>=2.4.7-beta1, <2.4.7-p8
<2.4.6-p13
1 listed version
2.4.9-alpha3
2.4.8-p3
2.4.7-p8
2.4.6-p13

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.