NVD / CVE Program· CNA Zabbix

CVE-2024-36465: SQL injection in Zabbix API

Noroxi assessment

Priority: Plan (action score 46/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 39.8% (FIRST EPSS); higher than 98.6% of all records.
Someone on the same network segment 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 7.0.8rc2, 7.2.2rc1.

Add it to your regular patch cycle. Upgrade to Zabbix Zabbix 7.0.8rc2, 7.2.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 low privilege (regular) Zabbix user with API access can use SQL injection vulnerability in include/classes/api/CApiService.php to execute arbitrary SQL commands via the groupBy parameter.

HighCVSS 8.6 · v4.0—No exploit Fix available

BDU:2025-05633

Published: Apr 2, 2025
Updated: Jun 17, 2026
EPSS: 39.8% · 98th percentile
CWE: CWE-89

Report tools

JSON

Action score

Plan

Add it to your regular patch cycle.

CVSS: 34 / 40 · 8.6 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 12 / 30 · 39.8%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · Zabbix: 8.6; NVD has not scored this yet; the score shown is the CNA’s.

CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

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
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

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 help

Affected 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 zabbix7.0.0 and later · up to 7.0.7 inclusive
zabbix zabbix7.2.0 and later · before 7.2.2
zabbix zabbix7.0.8

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
- 7.0.0 and later · up to and including 7.0.7affected · gitfixed in 7.0.8rc2
- 7.2.0 and later · up to and including 7.2.1affected · gitfixed in 7.2.2rc1

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:13	zabbix	before 1:7.0.9+dfsg-1	1:7.0.9+dfsg-1

Same product

zabbix: all records

Other 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 SAMLKEV
98Now
CVE-2022-23134Possible view of the setup pages by unauthenticated users if config file already existsKEV
80Now
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…
64This week

Published before and after this one in the same product

← EarlierCVE-2024-36464Nov 27, 2024 · Media Types: Office365, SMTP passwords are unencrypted and visible in plaintext when exported
10Monitor
← EarlierCVE-2024-36466Nov 28, 2024 · Unauthenticated Zabbix frontend takeover when SSO is being used
35Monitor
Later →CVE-2024-36469Apr 2, 2025 · User enumeration via timing attack in Zabbix web interface
9Monitor

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	7.0.8rc2	Vendor (CNA)
Zabbix Zabbix	7.2.2rc1	Vendor (CNA)
debian:zabbix	1:7.0.9+dfsg-1 · Debian:13	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

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.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

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 researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

cynau1treporter

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2024-42327126 days apartSQL injection in user.get API
63This week
CVE-2026-23921356 days apartBlind, read-only SQL injection in Zabbix API via sortfield parameter
35Monitor
CVE-2025-27240163 days apartSecondary-order SQL injection in Zabbix Server when deleting an autoregistered host
30Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Someone on the same network segment 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
Integrity
Availability

Attack vector: Adjacent
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: X

Weakness class (CWE)

CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

CVSS vector

CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const owner = req.query.owner;
2const rows = await db.query(
3  "SELECT * FROM files WHERE owner = '" + owner + "'"
4);

Fixed

1const owner = req.query.owner;
2const rows = await db.query(
3  "SELECT * FROM files WHERE owner = $1",
4  [owner]
5);

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)

ATT&CK techniques

—

Change log

Fix✗ → ✓Sep 28, 2026, 10:09 PM UTC

For records you follow, these changes also arrive as notifications. →

References

support.zabbix.com/browse/ZBX-26257

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records