CVE-2019-7869 json
Magento Stored Cross-site Scripting vulnerability in the admin panel
published 7y ago modified 4mo ago also GHSA-9f4p-3jgf-98f5 , EUVD-2022-3360
- cvss
- 4.8
- version 3.0, 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 vulnerability exists in the admin panel of 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 can be exploited by an authenticated user with permissions to manage customer groups.
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
Is CVE-2019-7869 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.56% chance of exploitation in the next 30 days, higher than 46% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 4.8 | CVSS:3.0/AV:N/AC:L/PR:H/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 | 4.8 | CVSS:3.0/AV:N/AC:L/PR:H/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.18 >=2.2.0, <2.2.9 >=2.3.0, <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-7869
advisory
-
github.com
/FriendsOfPHP/security-advisories/blob/master/magento/product-community-edition/CVE-2019-7869.yaml
web
-
github.com
/magento/magento2
package
Sources
- CVE List CVE-2019-7869
- GitHub Advisory GHSA-9f4p-3jgf-98f5
- NVD CVE-2019-7869
Fencer Intel 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.