CVE-2019-8109 json
Magento 2 Community Edition RCE Vulnerability via CSRF
published 7y ago modified 4mo ago also GHSA-x72m-p4qc-p7rv , EUVD-2022-5733
- cvss
- 8.0
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 58%
- public exploits
- 0
- none known
Summary
A remote code execution 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 can craft a malicious CSRF payload that can result in arbitrary command execution.
Patch / fix
- packagist magento/community-edition 2.2.10, 2.3.2-p1
- magento magento 2.2.10, 2.3.2
Is CVE-2019-8109 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.85% chance of exploitation in the next 30 days, higher than 58% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 8.0 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.0 | AV:N/AC:M/Au:S/C:P/I:P/A:P |
| GitHub | 3.1 | 8.0 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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-p1 |
2.2.10 2.3.2-p1 |
Affected products
- Adobe Systems Incorporated Magento 2
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
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-8109
advisory
-
github.com
/FriendsOfPHP/security-advisories/blob/master/magento/product-community-edition/CVE-2019-8109.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-8109
- GitHub Advisory GHSA-x72m-p4qc-p7rv
- NVD CVE-2019-8109
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.