CVE-2019-7861 json
Magento 2 Community Edition Unsafe File Upload
published 2019-08-02 7 y ago modified 2026-06-17 4 mo ago also GHSA-j837-vm6w-6qcv , EUVD-2022-4309
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.0%
- EPSS 2.0% chance of exploitation in 30 days, percentile 81%
- public exploits
- 0
- none known
Summary
Insufficient server-side validation of user input could allow an attacker to bypass file upload restrictions 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.
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
Exploit prediction
2.04% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
| GitHub | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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-434 Unrestricted Upload of File with Dangerous Type
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-7861
advisory
-
github.com
/FriendsOfPHP/security-advisories/blob/master/magento/product-community-edition/CVE-2019-7861.yaml
web
-
github.com
/magento/magento2
package
-
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-7861
- GitHub Advisory GHSA-j837-vm6w-6qcv
- NVD CVE-2019-7861
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.