Time Based SQL Injection in Zabbix Server Audit Log
Zabbix · Zabbix
Zabbix Server's audit log component fails to sanitise the "clientip" field, which is written into the Audit Log when a configured script is executed. An attacker who can reach the server and hold privileges sufficient to trigger script execution can inject SQL through that field to carry out time-based blind SQL injection, with no user interaction required.
Zabbix server can perform command execution for configured scripts. After command is executed, audit entry is added to "Audit Log". Due to "clientip" field is not sanitized, it is possible to injection SQL into "clientip" and exploit time based blind SQL injection.
- Exploited
- Yes, in VulnCheck KEV
- Reports
- 0
- Tactics
- 0/15
Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
First seen exploited 10 months after disclosure. Public exploit code (PoC-in-GitHub) appeared 3 days after disclosure.
- Disclosedday 0
- Public exploit codePoC-in-GitHub+3 days
- First seen exploitedVulnCheck KEV evidence+10 mo
MITRE ATT&CKA public catalogue of the techniques attackers use, maintained by MITRE. Patchfirst uses it to describe what attackers do with a vulnerability. techniques
No techniques linkedNo ATT&CK techniques are linked to this CVE yet. MITRE CTID has not mapped it, and no report passage in the corpus ties it to a technique.
What security researchers reported
Not named in any threat report yetAlso mentioned in 1 community threat pulse (AlienVault OTX)
Weaker evidencePulses are indicator collections that anyone can publish. A mention is not confirmation of exploitation.
- Midwest Malware26 Aug 2026