Cyber Resilience

CVE-2025-24414

High

Published: 11 February 2025

Published
11 February 2025
Modified
16 April 2025
KEV Added
Patch
CVSS Score v3.1 8.7 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N
EPSS Score 0.0132 80.3th percentile
Risk Priority 18 60% EPSS · 20% KEV · 20% CVSS

Summary

CVE-2025-24414 is a high-severity Cross-site Scripting (CWE-79) vulnerability in Adobe Commerce. Its CVSS base score is 8.7 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Browser Session Hijacking (T1185); ranked in the top 19.7% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified are NIST 800-53 SI-10 (Information Input Validation) and SI-15 (Information Output Filtering).

Deeper analysis

Adobe Commerce versions 2.4.8-beta1, 2.4.7-p3, 2.4.6-p8, 2.4.5-p10, 2.4.4-p11 and earlier contain a stored cross-site scripting vulnerability tracked as CVE-2025-24414. The flaw, assigned CWE-79, resides in form fields that accept and persist attacker-controlled input without adequate sanitization, allowing malicious JavaScript to be stored and later executed in the browsers of users who view the affected pages. The issue carries a CVSS 3.1 score of 8.7.

A low-privileged attacker with the ability to submit data through the vulnerable fields can inject scripts that execute in the context of other users, including administrators. Successful exploitation enables session takeover and yields high impact on both confidentiality and integrity while availability remains unaffected.

The Adobe security advisory APSB25-08, published alongside the CVE, details the affected releases and directs customers to the corresponding patched versions for remediation. The EPSS score has remained flat at 0.0132 with no observed increase since disclosure.

EU & UK References

Vulnerability details

Adobe Commerce versions 2.4.8-beta1, 2.4.7-p3, 2.4.6-p8, 2.4.5-p10, 2.4.4-p11 and earlier are affected by a stored Cross-Site Scripting (XSS) vulnerability that could be abused by a low-privileged attacker to inject malicious scripts into vulnerable form fields. Malicious JavaScript may be executed…

more

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 as high.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1185 Browser Session Hijacking Collection
Adversaries may take advantage of security vulnerabilities and inherent functionality in browser software to change content, modify user-behaviors, and intercept information as part of various browser session hijacking techniques.
Why these techniques?

Stored XSS enables injection of malicious JavaScript that executes in victim browsers, directly facilitating browser session hijacking and takeover as described.

Confidence: HIGH · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2025-24412Same product: Adobe Commerce
CVE-2025-24413Same product: Adobe Commerce
CVE-2026-21311Same product: Adobe Commerce
CVE-2025-24417Same product: Adobe Commerce
CVE-2025-24416Same product: Adobe Commerce
CVE-2025-24415Same product: Adobe Commerce
CVE-2025-24438Same product: Adobe Commerce
CVE-2026-34686Same product: Adobe Commerce
CVE-2026-21290Same product: Adobe Commerce
CVE-2026-21284Same product: Adobe Commerce

Affected Assets

adobe
commerce
2.4.4, 2.4.5, 2.4.6, 2.4.7, 2.4.8 · ≤ 2.4.4
adobe
commerce b2b
1.3.3, 1.3.4, 1.3.5, 1.4.2, 1.5.0 · ≤ 1.3.3
adobe
magento
2.4.4, 2.4.5, 2.4.6, 2.4.7, 2.4.8 · ≤ 2.4.4

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly addresses inadequate sanitization of vulnerable form fields by enforcing validation of user inputs to block malicious script injection.

prevent

Prevents execution of injected scripts in victims' browsers by filtering and encoding information outputs from stored content.

prevent

Ensures timely remediation of the specific stored XSS flaw in affected Adobe Commerce versions through identification, reporting, and patching.

References