Skip to main content
Public proof of conceptFix available

CVE-2024-42327

A public proof of concept exists; no exploitation attested.

  • Published2024-11-27
  • Fixed in7.0.1 · 6.4.17 · 6.0.32
  • WeaknessCWE-89

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2024-11-2712:15CVE publishedNVD
  2. 2025-04-16Exploit-DB entryExploit-DB

Versions per branch

NVD · CISA-ADP
Zabbix
BranchAffectedFixed in
7.0≥ 7.0.0, < 7.0.17.0.1
6.4≥ 6.4.0, < 6.4.176.4.17
6.0≥ 6.0.0, < 6.0.326.0.32
6.0≥ 6.0.0, ≤ 6.0.31no fix published
6.4≥ 6.4.0, ≤ 6.4.16no fix published
7.0≥ 7.0.0, ≤ 7.0.1no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As Zabbix, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • Zabbixother versions: not affected

    https://git.zabbix.com/

    Affected
    • ≥ 6.0.0, ≤ 6.0.31fixed in 6.0.32rc1git
    • ≥ 6.4.0, ≤ 6.4.16fixed in 6.4.17rc1git
    • ≥ 7.0.0, ≤ 7.0.1fixed in 7.0.2rc1git

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2024-11-27

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • zabbixUbuntu:Pro:22.04:LTSall versions · no fixed version listed
  • zabbixUbuntu:Pro:20.04:LTSall versions · no fixed version listed
  • zabbixDebian:14all versions · fixed in 1:7.0.1+dfsg-1
  • zabbixDebian:13all versions · fixed in 1:7.0.1+dfsg-1
  • zabbixDebian:12all versions · no fixed version listed
  • zabbixAlpine:v3.24from 7.0.0 · fixed in 7.0.1-r0
  • zabbixAlpine:v3.23from 7.0.0 · fixed in 7.0.1-r0
  • zabbixAlpine:v3.22from 7.0.0 · fixed in 7.0.1-r0

2 more package ranges on OSV.dev

Vendor advisories

  • CVE-2024-42327 Red Hat Product Security

    zabbix: SQL injection in user.get API

Full record on NVD

Fix

  1. Update Zabbix to 7.0.1 · 6.4.17 · 6.0.32

Advisories and patches

Detection

read 2026-11-11 10:17 UTC
Nuclei template
none so far
ProjectDiscovery
Exploit-DB
EDB-52230
Exploit-DB
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Published
2024-11-27
Last Modified
2026-06-17
NVD status
Analyzed
GitHub Advisory
GHSA-gx59-7g62-6xhg

Frequently asked questions

What is CVE-2024-42327?

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.

Is CVE-2024-42327 actively exploited?

Active exploitation of CVE-2024-42327 has not been confirmed. Its EPSS score was 79.1% on 2026-11-18, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2024-42327?

CVE-2024-42327 has a CVSS v3 base score of 9.9 (CRITICAL severity), with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H.

Running zabbix? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record