CVE-2019-7139

Exp

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.

Published: 2019-04-10 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2019-7139 is rated High Exploit Risk (83.1/100): CVSS Critical severity, with high exploitation likelihood (EPSS 17.44%, 97th percentile). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2019-7139

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2019-7139

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 60.11% 17.44% -42.67%
2 2026-03-17 62.99% 60.11% -2.89%
3 2026-03-04 — 62.99% —

Full EPSS history (49 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2019-7139

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.8 3.0 CRITICAL
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.9 [email protected]
7.5 2.0 HIGH
AV:N/AC:L/Au:N/C:P/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 10.0 6.4 [email protected]

Weakness enumeration for CVE-2019-7139

GitHub Security Advisory for CVE-2019-7139

GHSA-4j6w-9rf8-hg7r · Severity: critical · Ecosystem: composer — Magento 2 Community Edition SQLi Vulnerability

Affected software / configurations for CVE-2019-7139

Vendor Product Version Raw CPE
magento magento < 1.9.4.1 cpe:2.3:a:magento:magento:*:*:*:*:open_source:*:*:*
magento magento >= 1.14.0.0, < 1.14.4.1 cpe:2.3:a:magento:magento:*:*:*:*:commerce:*:*:*
magento magento >= 2.1.0, < 2.1.17 cpe:2.3:a:magento:magento:*:*:*:*:commerce:*:*:*
magento magento >= 2.1.0, < 2.1.17 cpe:2.3:a:magento:magento:*:*:*:*:open_source:*:*:*
magento magento >= 2.2.0, < 2.2.8 cpe:2.3:a:magento:magento:*:*:*:*:commerce:*:*:*
magento magento >= 2.2.0, < 2.2.8 cpe:2.3:a:magento:magento:*:*:*:*:open_source:*:*:*
magento magento >= 2.3.0, < 2.3.1 cpe:2.3:a:magento:magento:*:*:*:*:commerce:*:*:*
magento magento >= 2.3.0, < 2.3.1 cpe:2.3:a:magento:magento:*:*:*:*:open_source:*:*:*

References for CVE-2019-7139

cvelogic Threat Intelligence