CVE-2024-42327: SQL injection in user.get API
Noroxi assessment
Priority: This week (action score 63/100)
- Public proof-of-concept code exists (Exploit-DB, GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 79.1% (FIRST EPSS); higher than 99.6% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Zabbix Zabbix 6.0.32rc1, 6.4.17rc1, 7.0.2rc1.
Don’t wait for the next maintenance window. Upgrade to Zabbix Zabbix 6.0.32rc1, 6.4.17rc1, 7.0.2rc1 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
A non-admin user account on the Zabbix frontend with the default User role, or with any other role that gives API access can exploit this vulnerability. An SQLi exists in the CUser class in the addRelatedObjects function, this function is being called from the CUser.get function which is available for every user who has API access.
- Published
- Nov 27, 2024
- Updated
- Jun 17, 2026
- EPSS
- 79.1% · 99th percentile
- CWE
- CWE-89
Report tools
Action score
63
This week
Don’t wait for the next maintenance window.
- CVSS
- 39 / 40 · 9.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 24 / 30 · 79.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Zabbix
- 9.9
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi 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 zabbix6.0.0 and later · before 6.0.32
- zabbix zabbix6.4.0 and later · before 6.4.17
- zabbix zabbix7.0.0 and later · before 7.0.1
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Zabbix). Independent of NVD's CPE analysis and usually ahead of it.
Zabbix Zabbix
- 6.0.0 and later · up to and including 6.0.31affected · gitfixed in 6.0.32rc1
- 6.4.0 and later · up to and including 6.4.16affected · gitfixed in 6.4.17rc1
- 7.0.0 and later · up to and including 7.0.1affected · gitfixed in 7.0.2rc1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.20 | zabbix | from 6.0.0 · before 6.4.18-r0 | 6.4.18-r0 |
| Alpine:v3.21 | zabbix | from 6.0.0 · before 7.0.1-r0 | 7.0.1-r0 |
| Debian:12 | zabbix | from 0 | — |
| Debian:13 | zabbix | before 1:7.0.1+dfsg-1 | 1:7.0.1+dfsg-1 |
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-2016-10134SQL 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 t64This week
Published before and after this one in the same product
- ← EarlierCVE-2024-36468Nov 27, 2024 · Stack buffer overflow in zbx_snmp_cache_handle_engineid32Monitor
- ← EarlierCVE-2024-42326Nov 27, 2024 · Use after free vulnerability in browser.c17Monitor
- Later →CVE-2024-42328Nov 27, 2024 · JS - Crash on empty HTTP server response22Monitor
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 |
|---|---|---|
| Zabbix Zabbix | 6.0.32rc1 | Vendor (CNA) |
| Zabbix Zabbix | 6.4.17rc1 | Vendor (CNA) |
| Zabbix Zabbix | 7.0.2rc1 | Vendor (CNA) |
| alpine:zabbix | 6.4.18-r0 · Alpine:v3.20 | Package registry (OSV) |
| debian:zabbix | 1:7.0.1+dfsg-1 · Debian:13 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Exploit-DB entry ×1
- Proof-of-concept repository on GitHub ×11
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 |
|---|---|---|
| Exploit-DB entry | webapps | 2025-04-16 |
| Proof-of-concept repository on GitHub | stars:38 | 2024-12-01 |
| Proof-of-concept repository on GitHub | stars:18 | 2024-12-03 |
| Proof-of-concept repository on GitHub | stars:3 | 2024-12-06 |
| Proof-of-concept repository on GitHub | stars:3 | 2024-12-07 |
| Proof-of-concept repository on GitHub | stars:0 | 2024-12-11 |
| Proof-of-concept repository on GitHub | stars:0 | 2024-12-12 |
| Proof-of-concept repository on GitHub | stars:48 | 2025-01-01 |
| Proof-of-concept repository on GitHub | stars:9 | 2025-02-16 |
| Proof-of-concept repository on GitHub | stars:1 | 2025-04-18 |
| Proof-of-concept repository on GitHub | stars:0 | 2026-05-16 |
| Proof-of-concept repository on GitHub | stars:1 | 2026-06-09 |
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.
- Published
- First PoC+4 d
- TodayNov 9, 2026+712 d
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2024-36465126 days apartSQL injection in Zabbix API46Plan
- CVE-2026-23921482 days apartBlind, read-only SQL injection in Zabbix API via sortfield parameter35Monitor
- CVE-2025-27240289 days apartSecondary-order SQL injection in Zabbix Server when deleting an autoregistered host30Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
- CVE-2024-364661 days apartUnauthenticated Zabbix frontend takeover when SSO is being used35Monitor
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- 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
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Changed
- 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.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
nvd-secondary
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.