CVE-2019-7881 json
Magento 2 Community Edition XSS Vulnerability
published 2019-08-02 7 y ago modified 2026-06-17 4 mo ago also GHSA-7xqv-jgv6-x2h8 , EUVD-2022-3083
- cvss
- 5.4
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 68%
- public exploits
- 0
- none known
Summary
A cross-site scripting mitigation bypass exists in Magento 2.1 prior to 2.1.18, Magento 2.2 prior to 2.2.9, Magento 2.3 prior to 2.3.2. This could be exploited by an authenticated user to escalate privileges (admin vs. admin XSS attack).
Patch / fix
- packagist magento/community-edition 2.1.18, 2.2.9, 2.3.2
- magento magento 2.1.18, 2.2.9, 2.3.2
Exploit prediction
1.22% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 5.4 | CVSS:3.0/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.0 | 5.4 | CVSS:3.0/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, <2.1.18 >=2.2, <2.2.9 >=2.3, <2.3.2 |
2.1.18 2.2.9 2.3.2 |
Affected products
- n/a Magento 2
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
magento.com
/security/patches/magento-2.3.2-2.2.9-and-2.1.18-security-update-23
web, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-7881
advisory
-
github.com
/FriendsOfPHP/security-advisories/blob/master/magento/product-community-edition/CVE-2019-7881.yaml
web
-
web.archive.org
/web/20220121051916/https://magento.com/security/patches/magento-2.3.2-2.2.9-and-2.1.18-security-update-23
web
Sources
- CVE List CVE-2019-7881
- GitHub Advisory GHSA-7xqv-jgv6-x2h8
- NVD CVE-2019-7881
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.