dbcve.org
ZabbixApplication

CVE-2024-42327

CRITICAL · 9.9 CVSS v3.1 Published 2024-11-27
Fix available
A fix is available. Upgrade to 6.0.32 / 6.4.17 or later.
See remediation →
100/100
Remediation priority · Urgent
High EPSS Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in Zabbix frontend's CUser class addRelatedObjects function, exploitable through the CUser.get API method. Any user with API access (including default User role, which is non-admin) can exploit this to inject malicious SQL queries.

MitigationApply Zabbix security patch or upgrade to fixed version. Restrict or disable API access for non-admin users until patch is applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ZabbixApplication
Affected:>= 6.0.0, < 6.0.32>= 6.4.0, < 6.4.17>= 7.0.0, < 7.0.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed Zabbix version
    Check the Zabbix frontend version by logging into the web interface and navigating to the About page (Reports > System Information) or by checking the VERSION file in the Zabbix web directory. Alternatively, run 'zabbix_server --version' on the server if you have CLI access.
    Affected if The installed version falls within 6.0.0 to 6.0.31, 6.4.0 to 6.4.16, or 7.0.0.
  2. Verify API is enabled
    Check the Zabbix frontend configuration file (zabbix.conf.php) for the setting 'API_ENABLED' or similar API configuration. In the web interface, navigate to Administration > Users > Roles to review API access settings.
    Affected if The Zabbix API is enabled and accessible.
  3. Identify users with API access
    In the Zabbix web interface, go to Administration > Users > Users and review the roles assigned to each user. Check Administration > Users > Roles to see which roles have API access permissions enabled.
    Affected if Any non-admin user account (such as those with default User role) has API access enabled.
  4. Confirm CUser.get method is accessible
    Attempt a test API call using the CUser.get method with a low-privilege user account via curl or an API client, or review the API documentation settings in Administration > API information.
    Affected if The API accepts CUser.get requests from non-admin users.

A system is affected if it runs a vulnerable Zabbix version (6.0.0-6.0.31, 6.4.0-6.4.16, or 7.0.0) AND has the API enabled with non-admin users able to make API calls.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.0.32 / 6.4.17 / 7.0.1 or later
Fixed in 6.0.326.4.177.0.1
Interim mitigation

Apply Zabbix security patch or upgrade to fixed version. Restrict or disable API access for non-admin users until patch is applied.

Recommended fix High confidence

6.0.32 (for 6.0.x), 6.4.17 (for 6.4.x), or 7.0.1 (for 7.0.x)

  1. 1. Identify current Zabbix version by checking the Zabbix frontend (Adminstration > General > GUI) or running `zabbix_server -V`
  2. 2. Back up the Zabbix database (mysqldump/pg_dump) and configuration files (/etc/zabbix/)
  3. 3. Download the appropriate fixed version package from https://www.zabbix.com/download
  4. 4. Stop Zabbix services: `systemctl stop zabbix-server zabbix-agent httpd` (or `nginx` for web server)
  5. 5. Upgrade Zabbix packages using your package manager (apt/yum/dnf) for your OS distribution
  6. 6. Update Zabbix database schema if required: `zabbix_server --foreground --upgrade`
  7. 7. Start Zabbix services: `systemctl start zabbix-server zabbix-agent httpd`
  8. 8. Verify upgrade success: check Zabbix frontend and confirm version number matches fixed release
Caveat Patch upgrades within same major version (6.0.x to 6.0.32, 6.4.x to 6.4.17) typically have minimal breaking changes; upgrading to 7.0.x may require review of incompatibilities per Zabbix 7.0 release notes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Zabbix Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-42327 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-42327 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data