Skip to content
Fencer Intel
critical 9.8

CVE-2019-7139 in the critical feed json

Magento 2 Community Edition SQLi Vulnerability

published 7y ago modified 4mo ago also GHSA-4j6w-9rf8-hg7r , EUVD-2022-2395

cvss
9.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
22.2%
EPSS 22.2% chance of exploitation in 30 days, percentile 97%
public exploits
0
none known, plus a Nuclei check

Summary

An unauthenticated user can execute SQL statements that allow arbitrary read access to the underlying database, which causes sensitive data leakage. This issue is fixed 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 1.9.4.1, 1.14.4.1, 2.1.17, 2.2.8, 2.3.1

Is CVE-2019-7139 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 Fencer

Exploit prediction

22.24% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • Nuclei template Magento - SQL Injection nuclei detection template
  • ambionics.io https://www.ambionics.io/blog/magento-sqli referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P
GitHub 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/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

  • Magento Magento Open Source
  • Magento Magento Commerce
  • Magento Magento

Classification

Weakness
  • CWE-89 Improper Neutralization of Special Elements used in an SQL Command

References

Sources

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.