CVE-2022-24086
Adobe Commerce and Magento Open Source Improper Input Validation Vulnerability
Adobe Commerce and Magento Open Source
Adobe Commerce versions 2.4.3-p1 (and earlier) and 2.3.7-p2 (and earlier) are affected by an improper input validation vulnerability during the checkout process. Exploitation of this issue does not require user interaction and could result in arbitrary code execution.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 15 February 2022. US federal agencies were required to remediate it by 1 March 2022.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 99.2%, which is higher than 99.9% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Frequently asked questions
Is CVE-2022-24086 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2022-24086.
What does CVE-2022-24086 affect?
CVE-2022-24086 affects Adobe Commerce and Magento Open Source. Adobe Commerce versions 2.4.3-p1 (and earlier) and 2.3.7-p2 (and earlier) are affected by an improper input validation vulnerability during the checkout process. Exploitation of this issue does not require user interaction and could result in arbitrary code execution.
How severe is CVE-2022-24086?
CVE-2022-24086 is rated CRITICAL with a CVSS base score of 9.8. EPSS puts the probability of exploitation in the next 30 days at 99.2%, higher than 99.9% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 1 March 2022.
How should organisations respond to CVE-2022-24086?
Apply the vendor patch for Adobe Commerce and Magento Open Source as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.