CVE-2019-8127 json
Magento 2 Community Edition SQLi Vulnerability
published 2019-11-05 7 y ago modified 2026-06-17 4 mo ago also GHSA-2x2q-2xpv-mcf9 , EUVD-2022-2068
- cvss
- 8.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 69%
- public exploits
- 0
- none known
Summary
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. An authenticated user with privileges to an account with Newsletter Template editing permission could exfiltrate the Admin login data, and reset their password, effectively performing a privilege escalation.
Patch / fix
- packagist magento/community-edition 2.2.10, 2.3.2-p2
- magento magento 2.2.10, 2.3.2
Exploit prediction
1.26% chance of exploitation in the next 30 days, higher than 69% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.5 | AV:N/AC:L/Au:S/C:P/I:P/A:P |
| GitHub | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | magento/community-edition | >=2.2.0, <2.2.10 >=2.3.0, <2.3.2-p2 |
2.2.10 2.3.2-p2 |
Affected products
- Adobe Systems Incorporated Magento 2
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
-
magento.com
/security/patches/magento-2.3.3-and-2.2.10-security-update
web, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-8127
advisory
-
github.com
/FriendsOfPHP/security-advisories/blob/master/magento/product-community-edition/CVE-2019-8127.yaml
web
-
github.com
/magento/magento2
package
-
web.archive.org
/web/20220121051105/https://magento.com/security/patches/magento-2.3.3-and-2.2.10-security-update
web
Sources
- CVE List CVE-2019-8127
- GitHub Advisory GHSA-2x2q-2xpv-mcf9
- NVD CVE-2019-8127
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.