CVE-2019-8120 json
Magento 2 Community Edition XSS Vulnerability
published 2019-11-05 7 y ago modified 2026-06-17 4 mo ago also GHSA-985w-mqqp-7287 , EUVD-2022-3320
- cvss
- 5.4
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 46%
- public exploits
- 0
- none known
Summary
A stored cross-site scripting (XSS) vulnerability exists in Magento 2.1 prior to 2.1.19, Magento 2.2 prior to 2.2.10, Magento 2.3 prior to 2.3.3. An authenticated user can inject arbitrary Javascript code by manipulating section of a POST request related to customer's email address.
Patch / fix
- packagist magento/community-edition 2.1.19, 2.2.10, 2.3.3
- magento magento 2.1.19, 2.2.10
Exploit prediction
0.56% chance of exploitation in the next 30 days, higher than 46% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N |
| NVD | 2.0 | 3.5 | AV:N/AC:M/Au:S/C:N/I:P/A:N |
| GitHub | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | magento/community-edition | >=2.1.0, <2.1.19 >=2.2.0, <2.2.10 >=2.3.0, <2.3.3 |
2.1.19 2.2.10 2.3.3 |
Affected products
- Adobe Systems Incorporated Magento 2
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
magento.com
/security/patches/magento-2.3.3-and-2.2.10-security-update
web, patch, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-8120
advisory
-
github.com
/FriendsOfPHP/security-advisories/blob/master/magento/product-community-edition/CVE-2019-8120.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-8120
- GitHub Advisory GHSA-985w-mqqp-7287
- NVD CVE-2019-8120
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.