CVE-2019-7911 json
Magento 2 Community Edition Server-Side Request Forgery vulnerability
published 7y ago modified 4mo ago also GHSA-33cj-w75f-49m2 , EUVD-2022-2094
- cvss
- 7.2
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.4%
- EPSS 1.4% chance of exploitation in 30 days, percentile 73%
- public exploits
- 0
- none known
Summary
A server-side request forgery (SSRF) vulnerability exists in Magento Open Source prior to 1.9.4.2, and Magento Commerce prior to 1.14.4.2, 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 access to the admin panel to manipulate system configuration and execute arbitrary code.
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-7911 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
1.44% chance of exploitation in the next 30 days, higher than 73% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.2 | CVSS:3.0/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.0 | 7.2 | CVSS:3.0/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.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 1 Magento 2
Classification
- Weakness
-
- CWE-918 Server-Side Request Forgery
References
-
magento.com
/security/patches/magento-2.3.2-2.2.9-and-2.1.18-security-update-13
web, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-7911
advisory
-
github.com
/FriendsOfPHP/security-advisories/blob/master/magento/magento1ce/CVE-2019-7911.yaml
web
-
github.com
/FriendsOfPHP/security-advisories/blob/master/magento/magento1ee/CVE-2019-7911.yaml
web
-
github.com
/FriendsOfPHP/security-advisories/blob/master/magento/product-community-edition/CVE-2019-7911.yaml
web
-
web.archive.org
/web/20211206084839/https://magento.com/security/patches/magento-2.3.2-2.2.9-and-2.1.18-security-update-13
web
Sources
- CVE List CVE-2019-7911
- GitHub Advisory GHSA-33cj-w75f-49m2
- NVD CVE-2019-7911
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.