Loading vulnerability…
A SQL injection vulnerability exists in Zabbix versions prior to 2.2.14 and 3.0 before 3.0.4, specifically in the latest.php page. The vulnerability is due to improper sanitization of the toggle_ids array parameter, allowing remote attackers to inject arbitrary SQL commands. Exploitation is possible by authenticated users, and by unauthenticated users if guest mode is enabled.
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 auxiliary module targeting Zabbix 3.0.3 and earlier (CVE-2016-10134). The module exploits a SQL injection vulnerability in the 'toggle_ids[]' POST parameter of the Zabbix web interface. It authenticates to the Zabbix instance (optionally using provided credentials), crafts SQL injection payloads, and extracts usernames and password hashes from the backend database. The results are saved as a JSON file using Metasploit's loot mechanism. The module is written in Ruby and leverages Metasploit's HTTP client mixin. The main endpoints targeted are '/zabbix/index.php' for authentication and '/zabbix/latest.php' for the injection and data retrieval. The exploit is operational and provides real credential data if successful.
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.