CVE-2025-49557

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. These scripts may be used to escalate privileges within the application or compromise sensitive user data. Exploitation of this issue requires user interaction in that a victim must browse to the page containing the vulnerable field. Scope is changed.

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2025-49557 has a CVSS score of 8.7 (High). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.4.4-p15, 2.4.5-p14, 2.4.6-p12, 2.4.7-p7); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2025-49557? CVE-2025-49557 is a high-severity cross-site scripting (XSS) vulnerability in magento/community-edition (composer), affecting versions < 2.4.4-p15. It is fixed in 2.4.4-p15, 2.4.5-p14, 2.4.6-p12, 2.4.7-p7. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. How severe is CVE-2025-49557? CVE-2025-49557 has a CVSS score of 8.7 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2025-49557?
   • magento/community-edition (composer) (versions < 2.4.4-p15)
   • magento/project-community-edition (composer) (versions <= 2.0.2)
4. Is there a fix for CVE-2025-49557? Yes. CVE-2025-49557 is fixed in 2.4.4-p15, 2.4.5-p14, 2.4.6-p12, 2.4.7-p7. Upgrade to this version or later.
5. Is CVE-2025-49557 exploitable, and should I be worried? Whether CVE-2025-49557 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-49557 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-49557?
   • Upgrade magento/community-edition to 2.4.4-p15 or later
   • Upgrade magento/community-edition to 2.4.5-p14 or later
   • Upgrade magento/community-edition to 2.4.6-p12 or later
   • Upgrade magento/community-edition to 2.4.7-p7 or later