CVE-2019-8119 json
Magento 2 Community Edition RCE Vulnerability
published 2019-11-05 7 y ago modified 2026-06-17 4 mo ago also GHSA-j63v-wcf9-c9hm , EUVD-2022-4286
- cvss
- 7.2
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.9%
- EPSS 1.9% chance of exploitation in 30 days, percentile 79%
- public exploits
- 0
- none known
Summary
A remote code execution 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 admin user with import product privileges can delete files through bulk product import and inject code into XSLT file. The combination of these manipulations can lead to remote code execution.
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
1.85% chance of exploitation in the next 30 days, higher than 79% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:H/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 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
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
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-8119
advisory
-
github.com
/FriendsOfPHP/security-advisories/blob/master/magento/product-community-edition/CVE-2019-8119.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-8119
- GitHub Advisory GHSA-j63v-wcf9-c9hm
- NVD CVE-2019-8119
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.