CVE-2020-3719 json
Magento sql injection vulnerability
published 2020-01-29 6 y ago modified 2026-09-08 2 mo ago also BIT-magento-2020-3719 , EUVD-2022-5223 , GHSA-rr59-pjwj-6grj
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.2%
- EPSS 3.2% chance of exploitation in 30 days, percentile 88%
- public exploits
- 0
- none known
Summary
Magento versions 2.3.3 and earlier, 2.2.10 and earlier, 1.14.4.3 and earlier, and 1.9.4.3 and earlier have an sql injection vulnerability. Successful exploitation could lead to sensitive information disclosure.
Patch / fix
- packagist magento/community-edition 2.2.11, 2.3.4
- packagist magento/core 1.9.4.4
- bitnami magento 2.2.11, 2.3.4
Exploit prediction
3.16% chance of exploitation in the next 30 days, higher than 88% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 7.8 | AV:N/AC:L/Au:N/C:C/I:N/A:N |
| OSV | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | magento/community-edition | >=2.3.0, <2.3.4 <2.2.11 |
2.3.4 2.2.11 |
| packagist | magento/core | <1.9.4.4 |
1.9.4.4 |
| bitnami | magento | >=2.2.0, <2.2.11 >=2.3.0, <2.3.4 |
2.2.11 2.3.4 |
Affected products
- Adobe Magento
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
-
helpx.adobe.com
/security/products/magento/apsb20-02.html
web, patch, vendor-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-3719
advisory, web
-
github.com
/magento/magento2
package
Sources
- CVE List CVE-2020-3719
- GitHub Advisory GHSA-rr59-pjwj-6grj
- NVD CVE-2020-3719
- OSV BIT-magento-2020-3719
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.