How severe is CVE-2019-7139?

CVE-2019-7139 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2019-7139?

CVE-2019-7139 affects the following packages: magento/community-edition (Packagist), magento/community-edition (Packagist), magento/community-edition (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2019-7139?

Update magento/community-edition to 2.1.18 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-7139 is resolved across your whole dependency graph.

How do I detect CVE-2019-7139 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for magento/community-edition, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2019-7139 if there is no patch (or I can't update yet)?

Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Is CVE-2019-7139 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2019-7139, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2019-7139?

CVE-2019-7139 has an EPSS (Exploit Prediction Scoring System) score of 22.2%, placing it in the 98th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2019-7139?

CVE-2019-7139 is classified as SQL Injection (CWE-89). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for CVE-2019-7139?

A Nuclei detection template exists for CVE-2019-7139, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2019-7139 published, and has it been updated?

CVE-2019-7139 was published on April 10, 2019 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

CRITICAL severity

CVE-2019-7139 — community-edition

CRITICAL

CVE-2019-7139 is a critical-severity (CVSS 9.8) SQL Injection vulnerability in magento/community-edition. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for magento/community-edition — see the affected versions and patch details below.

Magento 2 Community Edition SQLi Vulnerability

Also known asGHSA-4j6w-9rf8-hg7r

Published

Apr 10, 2019

Updated

Oct 24, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

2 known

Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

22.2%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs98th percentile — riskier than 98% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected

🐘magento/community-edition🐘magento/community-edition🐘magento/community-edition

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`magento/community-edition`	≥ 2.1.0&&< 2.1.18	2.1.18`composer require magento/community-edition:^2.1.18`
🐘Packagist	`magento/community-edition`	≥ 2.2.0&&< 2.2.9	2.2.9`composer require magento/community-edition:^2.2.9`
🐘Packagist	`magento/community-edition`	≥ 2.3.0&&< 2.3.2	2.3.2`composer require magento/community-edition:^2.3.2`

Affected Products

1 product · 8 configurations

Application

magentomagento

≥ 2.3.0 && < 2.3.1

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

An unauthenticated user can execute SQL statements that allow arbitrary …

ambionics.ioNVDAug 2019

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for magento/community-edition, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update magento/community-edition to 2.1.18 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-7139 is resolved across your whole dependency graph.
Workarounds
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

How to detect CVE-2019-7139

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2019-7139 -u https://target

Template: Magento - SQL Injection
Severity: critical
Impact: Unauthenticated attackers can execute SQL injection to extract sensitive database contents including customer information, payment details, and administrative credentials, potentially leading to complete store compromise.
Remediation: 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.

Template by ProjectDiscovery nuclei-templates (MaStErChO), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2019-7139 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

9.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CWE Classification

Weaponization

OpenSSF Scorecard

Package health score

security-advisories

4.8/10

Maintained10/10

Code-Review10/10

Branch-Protection0/10

Assessed Nov 2, 2026

Timeline

Disclosed

Apr 10, 2019

First exploit

Aug 6, 2019

Last updated

Oct 24, 2026

Identifiers

CVE-2019-7139

GHSA-4j6w-9rf8-hg7r

References

Advisorynvd.nist.gov · CVE 2019 7139 Webmagento.com · magento 2.3.2 2.2.9 and 2.1.18 security update 13 Webgithub.com · CVE 2019 7139.yaml Webgithub.com · CVE 2019 7139.yaml Webgithub.com · CVE 2019 7139.yaml Webmagento.com · supee 11086 Webweb.archive.org · magento 2.3.2 2.2.9 and 2.1.18 security update 13 Packagegithub.com · magento2 Evidenceambionics.io · magento sqli

Related vulnerabilities

This CVE is critical severity; 1 of 8 other CVEs affecting magento/community-edition is rated as high or higher (top: critical).

CVE-2025-54264CVE-2025-54263CVE-2025-54266CVE-2025-54267CVE-2025-54265CVE-2025-54236CVE-2025-49555CVE-2025-49556

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2019-7139 — community-edition

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

How to detect CVE-2019-7139

Frequently Asked Questions

Is CVE-2019-7139 in your dependencies?