First published: Fri Oct 13 2023(Updated: )
Adobe Commerce versions 2.4.7-beta1 (and earlier), 2.4.6-p2 (and earlier), 2.4.5-p4 (and earlier) and 2.4.4-p5 (and earlier) are affected by an Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability that could lead in arbitrary code execution by an admin-privilege authenticated attacker. Exploitation of this issue does not require user interaction and attack complexity is high as it requires knowledge of tooling beyond just using the UI.
Credit: psirt@adobe.com
Affected Software | Affected Version | How to fix |
---|---|---|
Adobe Magento Commerce | =2.3.7 | |
Adobe Magento Commerce | =2.3.7-p1 | |
Adobe Magento Commerce | =2.3.7-p2 | |
Adobe Magento Commerce | =2.3.7-p3 | |
Adobe Magento Commerce | =2.3.7-p4 | |
Adobe Magento Commerce | =2.3.7-p4-ext1 | |
Adobe Magento Commerce | =2.3.7-p4-ext2 | |
Adobe Magento Commerce | =2.3.7-p4-ext3 | |
Adobe Magento Commerce | =2.3.7-p4-ext4 | |
Adobe Magento Commerce | =2.4.0 | |
Adobe Magento Commerce | =2.4.0-ext-1 | |
Adobe Magento Commerce | =2.4.0-ext-2 | |
Adobe Magento Commerce | =2.4.0-ext-3 | |
Adobe Magento Commerce | =2.4.0-ext-4 | |
Adobe Magento Commerce | =2.4.1 | |
Adobe Magento Commerce | =2.4.1-ext-1 | |
Adobe Magento Commerce | =2.4.1-ext-2 | |
Adobe Magento Commerce | =2.4.1-ext-3 | |
Adobe Magento Commerce | =2.4.1-ext-4 | |
Adobe Magento Commerce | =2.4.2 | |
Adobe Magento Commerce | =2.4.2-ext-1 | |
Adobe Magento Commerce | =2.4.2-ext-2 | |
Adobe Magento Commerce | =2.4.2-ext-3 | |
Adobe Magento Commerce | =2.4.2-ext-4 | |
Adobe Magento Commerce | =2.4.3 | |
Adobe Magento Commerce | =2.4.3-ext-1 | |
Adobe Magento Commerce | =2.4.3-ext-2 | |
Adobe Magento Commerce | =2.4.3-ext-3 | |
Adobe Magento Commerce | =2.4.3-ext-4 | |
Adobe Magento Commerce | =2.4.4 | |
Adobe Magento Commerce | =2.4.4-p1 | |
Adobe Magento Commerce | =2.4.4-p2 | |
Adobe Magento Commerce | =2.4.4-p3 | |
Adobe Magento Commerce | =2.4.4-p4 | |
Adobe Magento Commerce | =2.4.4-p5 | |
Adobe Magento Commerce | =2.4.5 | |
Adobe Magento Commerce | =2.4.5-p1 | |
Adobe Magento Commerce | =2.4.5-p2 | |
Adobe Magento Commerce | =2.4.5-p3 | |
Adobe Magento Commerce | =2.4.5-p4 | |
Adobe Magento Commerce | =2.4.5-p5 | |
Adobe Magento Commerce | =2.4.6 | |
Adobe Magento Commerce | =2.4.6-p1 | |
Adobe Magento Commerce | =2.4.6-p2 | |
Adobe Magento Commerce | =2.4.7-b1 | |
Adobe Magento Open Source | =2.4.4 | |
Adobe Magento Open Source | =2.4.4-p1 | |
Adobe Magento Open Source | =2.4.4-p2 | |
Adobe Magento Open Source | =2.4.4-p3 | |
Adobe Magento Open Source | =2.4.5 | |
Adobe Magento Open Source | =2.4.5-p1 | |
Adobe Magento Open Source | =2.4.5-p2 | |
Adobe Magento Open Source | =2.4.5-p3 | |
Adobe Magento Open Source | =2.4.5-p4 | |
Adobe Magento Open Source | =2.4.6 | |
Adobe Magento Open Source | =2.4.6-p1 | |
Adobe Magento Open Source | =2.4.6-p2 | |
Adobe Magento Open Source | =2.4.7-b1 | |
Adobe Magento Commerce | =2.4.4 | |
Adobe Magento Commerce | =2.4.4-p1 | |
Adobe Magento Commerce | =2.4.4-p2 | |
Adobe Magento Commerce | =2.4.4-p3 | |
Adobe Magento Commerce | =2.4.5 | |
Adobe Magento Commerce | =2.4.5-p1 | |
Adobe Magento Commerce | =2.4.5-p2 | |
Adobe Magento Commerce | =2.4.5-p3 | |
Adobe Magento Commerce | =2.4.5-p4 | |
Adobe Magento Commerce | =2.4.6 | |
Adobe Magento Commerce | =2.4.6-p1 | |
Adobe Magento Commerce | =2.4.6-p2 | |
Adobe Magento Commerce | =2.4.7-b1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2023-38250 is classified as a critical severity vulnerability due to its potential for arbitrary code execution through SQL injection.
To fix CVE-2023-38250, upgrade to the latest patched version of Adobe Commerce or Magento Open Source as specified in Adobe's security advisory.
CVE-2023-38250 affects Adobe Commerce versions 2.4.7-beta1 and earlier, along with versions 2.4.6-p2, 2.4.5-p4, and 2.4.4-p5 among others.
If CVE-2023-38250 is exploited, it could allow attackers to execute arbitrary code on the affected system.
There are no known workarounds for CVE-2023-38250; the recommended action is to apply the latest updates.