Magento SQL injection vulnerability
A SQL injection vulnerability exists in Magento 2.2 prior to 2.2.10, Magento 2.3 prior to 2.3.3 or 2.3.2-p1. A user with store manipulation privileges can execute arbitrary SQL queries by getting access to the database connection through group instance in email templates.
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| Composer package | magento/community-edition | >= 2.2.0, < 2.2.10, >= 2.3.0, < 2.3.2-p1 | 2.2.10, 2.3.2-p1 |
| Magento (core) | magento/community-edition | >= 2.2.0, < 2.2.10, >= 2.3.0, < 2.3.2-p1 | 2.2.10, 2.3.2-p1 |
References
- https://nvd.nist.gov/vuln/detail/CVE-2019-8130
- https://github.com/FriendsOfPHP/security-advisories/blob/master/magento/product-community-edition/CVE-2019-8130.yaml
- https://github.com/magento/magento2
- https://web.archive.org/web/20210616202033/https://magento.com/security/patches/magento-2.3.3-and-2.2.10-security-update
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H- Weakness (CWE)
CWE-89- Platform
- Composer, Magento
- Package
magento/community-edition- Disclosed
- 24.05.2022
- Updated
- 11.10.2026 11:18
Sources and licenses
OSV / GitHub Advisory Database - GHSA-x42g-82pp-4v6g - CC BY 4.0
Vulnerability history: magento/community-edition
All published vulnerabilities of this package (Composer package), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 360
- First → latest
- 11.2019 10.2025
- Without a fix
- 3
- Exploited in attacks
- 3
Severity breakdown
- Critical 47
- High 104
- Medium 192
- Low 17
Disclosures per year
- 2019: 7
- 2020: 0
- 2021: 0
- 2022: 214
- 2023: 32
- 2024: 62
- 2025: 45
- 2026: 0
-
Magento SQL injection vulnerability this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.