CVE-2025-54264: Adobe Commerce | Cross-site Scripting (Stored XSS) (CWE-79)
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.
Other sources
Magento 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) 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.
— GitHub
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-54264?
CVE-2025-54264 is classified as a high-severity vulnerability due to its potential for exploitation by high-privileged attackers.
How do I fix CVE-2025-54264?
To fix CVE-2025-54264, upgrade to Adobe Commerce version 2.4.9 or later to mitigate the stored Cross-Site Scripting vulnerability.
Who is affected by CVE-2025-54264?
CVE-2025-54264 affects Adobe Commerce versions prior to 2.4.9-alpha2.
What is the impact of exploiting CVE-2025-54264?
Exploitation of CVE-2025-54264 allows attackers to inject malicious scripts that could lead to data theft or site compromise.
Is there a workaround for CVE-2025-54264?
Currently, there are no known workarounds for CVE-2025-54264 other than upgrading to the patched version.