CVE-2023-38250: Magento Open Source allows SQL Injection
8.1
Basic Information
Technical Details
| Package Name | Ecosystem | Vulnerable Versions | First Patched Version |
|---|---|---|---|
| magento/community-edition | composer | = 2.4.7-beta1 | 2.4.7-beta2 |
| magento/community-edition | composer | = 2.4.7 | |
| magento/community-edition | composer | = 2.4.6 | |
| magento/community-edition | composer | = 2.4.5 | |
| magento/community-edition | composer | = 2.4.4 | |
| magento/community-edition | composer | >= 2.4.6-p1, < 2.4.6-p3 | 2.4.6-p3 |
| magento/community-edition | composer | >= 2.4.5-p1, < 2.4.5-p5 | 2.4.5-p5 |
| magento/community-edition | composer | >= 2.4.4-p1, < 2.4.4-p6 | 2.4.4-p6 |
| magento/project-community-edition | composer | <= 2.0.2 |
Vulnerability Intelligence
Miggo AI
Root Cause Analysis
The provided vulnerability information lacks critical technical details needed to identify specific vulnerable functions. While the CWE-89 classification confirms SQL injection exists, there are no commit diffs, patch details, or code examples showing the vulnerable implementation. The advisory mentions exploitation requires admin privileges and non-UI tooling knowledge, suggesting the vulnerability might exist in backend/admin controllers or data processing utilities, but without concrete evidence of: 1) raw SQL query construction patterns, 2) parameter binding bypasses, or 3) specific user input handling methods, we cannot confidently identify exact functions. Magento's architecture typically uses ORM/Zend_Db abstractions that prevent SQLi, so the vulnerability likely involves an edge case where these protections were bypassed - but the absence of patch details makes confirmation impossible.