First published: Thu Oct 15 2020(Updated: )
Magento versions 2.4.0 and 2.3.5 (and earlier) are affected by an SQL Injection vulnerability that could lead to sensitive information disclosure. This vulnerability could be exploited by an authenticated user with permissions to the product listing page to read data from the database.
Credit: psirt@adobe.com
Affected Software | Affected Version | How to fix |
---|---|---|
composer/magento/community-edition | =2.4.0 | 2.4.1 |
composer/magento/community-edition | <2.3.6 | 2.3.6 |
CentOS Libgcc | <2.3.5 | |
CentOS Libgcc | <2.3.5 | |
CentOS Libgcc | =2.3.5 | |
CentOS Libgcc | =2.3.5 | |
CentOS Libgcc | =2.4.0 | |
CentOS Libgcc | =2.4.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2020-24400 refers to an SQL Injection vulnerability in Magento versions 2.4.0 and 2.3.5 (and earlier) that could allow an authenticated user to access sensitive information from the database.
The severity of CVE-2020-24400 is rated as high with a CVSS score of 7.1.
CVE-2020-24400 affects Magento versions 2.4.0 and 2.3.5 (and earlier), potentially allowing an authenticated user with permissions to the product listing page to read data from the database.
The SQL Injection vulnerability in Magento can be exploited by an authenticated user with permissions to the product listing page to execute arbitrary SQL queries and retrieve sensitive information.
Yes, a fix is available for CVE-2020-24400. It is recommended to update Magento to versions 2.4.1 or 2.3.6 (or later) to mitigate the vulnerability.