Loading vulnerability…
Multiple SQL injection vulnerabilities exist in Zabbix versions 1.8.x before 1.8.18rc1, 2.0.x before 2.0.9rc1, and 2.1.x before 2.1.7. The vulnerabilities allow attackers to inject arbitrary SQL commands via unspecified vectors in the affected versions of Zabbix.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository contains a single Metasploit module (modules/exploits/linux/http/zabbix_sqli.rb) targeting Zabbix versions 2.0.8 and below. The exploit leverages an unauthenticated SQL injection vulnerability (CVE-2013-5743) in the Zabbix web interface to extract an active administrator session ID. Using this session, the module uploads a script containing an attacker-supplied payload via the scripts.php endpoint and then executes it through scripts_exec.php, achieving remote code execution as the web server user. The module also includes cleanup functionality to remove the uploaded script after exploitation. The exploit is operational, allowing arbitrary command execution, and is designed for use within the Metasploit framework. The main attack vector is network-based, requiring HTTP access to the vulnerable Zabbix instance. The code is written in Ruby and is structured as a typical Metasploit exploit module.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.