CVE-2025-49554
Published: 12 August 2025
Summary
CVE-2025-49554 is a high-severity Improper Input Validation (CWE-20) vulnerability in Adobe Commerce. Its CVSS base score is 7.5 (High).
Operationally, ranked in the top 22.5% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis
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 an Improper Input Validation vulnerability tracked as CVE-2025-49554. The flaw, assigned CWE-20 and carrying a CVSS 3.1 score of 7.5, allows specially crafted input to trigger an application crash or unresponsiveness, directly impacting availability while leaving confidentiality and integrity untouched.
An unauthenticated remote attacker can exploit the issue over the network with low complexity and no user interaction required, simply by sending the malicious payload to cause denial-of-service.
The Adobe security advisory at https://helpx.adobe.com/security/products/magento/apsb25-71.html addresses remediation for the affected Magento-based Commerce installations. The associated EPSS score has remained flat at 0.0100 with no material rise observed since disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-24450
Vulnerability details
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 an Improper Input Validation vulnerability that could lead to application denial-of-service. An attacker could exploit this vulnerability by providing specially crafted input, causing the application to…
more
crash or become unresponsive. Exploitation of this issue does not require user interaction.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Security testing and developer training directly verify and enforce proper input validation, reducing exploitability of injection and malformed-data weaknesses.
Security testing and evaluation at multiple SDLC stages directly detects missing or flawed input validation, with the required remediation process ensuring fixes are applied.
Directly implements checks on information inputs to reject invalid data before processing.
Spam protection mechanisms perform filtering and detection on inbound/outbound messages, directly compensating for missing or weak input validation of unsolicited content.