First published: Fri Jun 26 2020(Updated: )
Magento versions 2.3.4 and earlier, 2.2.11 and earlier (see note), 1.14.4.4 and earlier, and 1.9.4.4 and earlier have a business logic error vulnerability. Successful exploitation could lead to privilege escalation.
Credit: psirt@adobe.com psirt@adobe.com
Affected Software | Affected Version | How to fix |
---|---|---|
composer/magento/core | <1.9.4.5 | 1.9.4.5 |
composer/magento/community-edition | >=2.3.0<2.3.4-p2 | 2.3.4-p2 |
composer/magento/community-edition | <=2.2.11 | |
Magento Magento | <=1.9.4.4 | |
Magento Magento | <=1.14.4.4 | |
Magento Magento | >=2.2.0<=2.2.11 | |
Magento Magento | >=2.2.0<=2.2.11 | |
Magento Magento | >=2.3.0<=2.3.4 | |
Magento Magento | >=2.3.0<=2.3.4 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2020-9630 is a business logic error vulnerability in Magento versions 2.3.4 and earlier, 2.2.11 and earlier, 1.14.4.4 and earlier, and 1.9.4.4 and earlier.
The severity of CVE-2020-9630 is critical with a CVSS score of 9.8.
Successful exploitation of CVE-2020-9630 could lead to privilege escalation.
Magento versions 2.3.4 and earlier, 2.2.11 and earlier, 1.14.4.4 and earlier, and 1.9.4.4 and earlier are affected by CVE-2020-9630.
Yes, upgrading to Magento versions 2.3.5 or 2.2.12 or later will fix CVE-2020-9630.