Loading vulnerability…
CVE-2019-7139 is an SQL injection vulnerability in Magento 2 Community Edition. An unauthenticated user can execute SQL statements that provide arbitrary read access to the underlying database. Affected releases are Magento 2.1 before 2.1.18, Magento 2.2 before 2.2.9, and Magento 2.3 before 2.3.2.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
2 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos.
This small three-file Python proof-of-concept repository targets CVE-2019-7139 (PRODSECBUG-2198), an unauthenticated SQL injection issue in Magento's product frontend synchronization endpoint. The README documents affected Magento releases and usage, while exploit.py contains all exploit logic; LICENSE is MIT. The script uses requests with TLS certificate verification disabled and optionally supports a proxy through the Browser.PROXY class attribute. It first tests both error-based (HTTP 400) and time-based (greater than 1.5-second delay using SLEEP) SQL-injection oracles. Once an oracle is found, it brute-forces expression lengths and characters to enumerate schemas, tables, columns, and limited sample data. It is an active data-extraction exploit rather than a mere vulnerability detector; it does not provide command execution, persistence, or a shell payload.
This repository is a proof-of-concept exploit for CVE-2019-7139, an unauthenticated SQL injection vulnerability in Magento. The main file, exploit.py, is a Python script that targets the /catalog/product_frontend_action/synchronize endpoint of a Magento installation. By sending specially crafted GET requests with SQL injection payloads in the 'ids[0][product_id][to]' parameter, the script can enumerate database names, table names, column names, and extract sample data from the database. The exploit supports both error-based and time-based SQL injection techniques, automatically selecting the most reliable method. The script is designed for educational and research purposes and requires only the target URL as input. The repository also includes a README.md with detailed usage instructions and a LICENSE file. No hardcoded credentials or IP addresses are present; the only fingerprintable endpoint is the vulnerable Magento path. The exploit is a POC and does not provide weaponized or post-exploitation capabilities.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.