CVE-2019-7851 json
Magento 2 Community Edition CSRF vulnerability
published 7y ago modified 4mo ago also GHSA-mhvf-j94g-3qp7 , EUVD-2022-4570
- cvss
- 6.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 38%
- public exploits
- 0
- none known
Summary
A cross-site request forgery vulnerability 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 can lead to unintended data deletion from customer pages.
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-7851 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.44% chance of exploitation in the next 30 days, higher than 38% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 6.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N |
| NVD | 2.0 | 5.8 | AV:N/AC:M/Au:N/C:N/I:P/A:P |
| GitHub | 3.0 | 6.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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-352 Cross-Site Request Forgery
References
-
magento.com
/security/patches/magento-2.3.2-2.2.9-and-2.1.18-security-update-33
web, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-7851
advisory
-
github.com
/FriendsOfPHP/security-advisories/blob/master/magento/product-community-edition/CVE-2019-7851.yaml
web
-
github.com
/magento/magento2
package
-
web.archive.org
/web/20220121011306/https://magento.com/security/patches/magento-2.3.2-2.2.9-and-2.1.18-security-update-33
web
Sources
- CVE List CVE-2019-7851
- GitHub Advisory GHSA-mhvf-j94g-3qp7
- NVD CVE-2019-7851
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.