CVE-2016-10134: SQL injection vulnerability in Zabbix before 2.2.14 and 3.0 before 3.0.4 allows remote attackers to execute arbitrary SQL commands via the…
Noroxi assessment
Priority: This week (action score 64/100)
- A ready-made attack module is public (Metasploit, Nuclei); exploiting it takes no special expertise.
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 82.6% (FIRST EPSS); higher than 99.6% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: zabbix (Alpine:v3.10) 3.0.4-r0; zabbix (Debian:12) 1:3.0.4+dfsg-1; zabbix (Debian:8) 1:2.2.7+dfsg-2+deb8u2.
Don’t wait for the next maintenance window. Upgrade to zabbix (Alpine:v3.10) 3.0.4-r0; zabbix (Debian:12) 1:3.0.4+dfsg-1; zabbix (Debian:8) 1:2.2.7+dfsg-2+deb8u2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
SQL injection vulnerability in Zabbix before 2.2.14 and 3.0 before 3.0.4 allows remote attackers to execute arbitrary SQL commands via the toggle_ids array parameter in latest.php.
- Published
- Feb 16, 2017
- Updated
- Jun 16, 2026
- EPSS
- 82.6% · 99th percentile
- CWE
- CWE-89
Report tools
Action score
64
Don’t wait for the next maintenance window.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 25 / 30 · 82.6%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Weaponized exploit exists
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| zabbix | zabbix | cpe:2.3:a:zabbix:zabbix |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- zabbix zabbixup to 2.2.13 inclusive
- zabbix zabbix3.0.0
- zabbix zabbix3.0.1
- zabbix zabbix3.0.2
- zabbix zabbix3.0.3
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.10 | zabbix | before 3.0.4-r0 | 3.0.4-r0 |
| Debian:12 | zabbix | before 1:3.0.4+dfsg-1 | 1:3.0.4+dfsg-1 |
| Debian:8 | zabbix | before 1:2.2.7+dfsg-2+deb8u2 | 1:2.2.7+dfsg-2+deb8u2 |
Same product
zabbix: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-23131Unsafe client-side session storage leading to authentication bypass/instance takeover via Zabbix Frontend with configured SAMLKEV98Now
- CVE-2022-23134Possible view of the setup pages by unauthenticated users if config file already existsKEV80Now
- CVE-2024-42327SQL injection in user.get API63This week
Published before and after this one in the same product
- ← EarlierCVE-2014-9450Jan 2, 2015 · Multiple SQL injection vulnerabilities in chart_bar.php in the frontend in Zabbix before 1.8.22, 2.0.x before 2.0.14, and 2.2.x before…30Monitor
- ← EarlierCVE-2016-4338Jan 23, 2017 · The mysql user parameter configuration script (userparameter_mysql.conf) in the agent in Zabbix before 2.0.18, 2.2.x before 2.2.13, and 3.0.40Plan
- Later →CVE-2017-2824May 24, 2017 · An exploitable code execution vulnerability exists in the trapper command functionality of Zabbix Server 2.4.X.40Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:zabbix | 3.0.4-r0 · Alpine:v3.5 | Package registry (OSV) |
| debian:zabbix | 1:3.0.4+dfsg-1 · Debian:12 | Package registry (OSV) |
Exploit status
Weaponized
A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.
Evidence
- Metasploit module ×1
- Nuclei detection template ×1
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Metasploit module | auxiliary/gather/zabbix_toggleids_sqliZabbix toggle_ids SQL Injectionauxiliary | 2016-08-11 |
| Nuclei detection template | Nuclei template CVE-2016-10134 | — |
| Proof-of-concept repository on GitHub | stars:0 | 2026-10-08 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Metasploit-190 d
- Published
- First PoC+3520 d
- TodayNov 14, 2026+3557 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')CVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
The query text is built by concatenating user input. The database cannot tell where the data ends and the command begins.
The bug in code
The whole CWE-89 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const owner = req.query.owner;
const rows = await db.query(
"SELECT * FROM files WHERE owner = '" + owner + "'"
);Fixed
const owner = req.query.owner;
const rows = await db.query(
"SELECT * FROM files WHERE owner = $1",
[owner]
);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Object Relational Mapping InjectionCAPEC-109likelihood: Low · High
- SQL Injection through SOAP Parameter TamperingCAPEC-110likelihood: High · Very High
- Expanding Control over the Operating System from the DatabaseCAPEC-470Very High
- SQL InjectionCAPEC-66likelihood: High · High
- Blind SQL InjectionCAPEC-7likelihood: High · High
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.