CVE-2019-7139
A permanent, source-backed tracker page. Values are shown only when returned; explicit gaps and read failures remain different states.
What it is
ReportedAn 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. Source description excerpt; complete tracked detail loads below.
NVD published: Apr 10, 2019 · Source record updated: Aug 8, 2026 · Tracker snapshot: Aug 8, 2026
What is affected
Reportedmagento — magento. Product-level identification only; no affected-version conclusion is available from this field.
NVD published: Apr 10, 2019 · Source record updated: Aug 8, 2026 · Tracker snapshot: Aug 8, 2026
Urgency and basis
ReportedAct · 457.3
Tracker decision tier from the evidence detailed below · Source record updated: Aug 8, 2026 · Tracker snapshot: Aug 8, 2026
Exploitation evidence
Reportedkev-listed · VulnCheck KEV
VulnCheck KEV added: Apr 2, 2019 · Source record updated: Aug 8, 2026 · Tracker snapshot: Aug 8, 2026
What to do
ReportedApply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable.
Tracked source remediation field · Source record updated: Aug 8, 2026 · Tracker snapshot: Aug 8, 2026
Evidence detail
Loading the full tracker evidence record…