← Vulnerability feed

Vulnerability record · CVE-2024-42327 · published 27 November 2024

CVE-2024-42327: Zabbix frontend SQL injection in CUser addRelatedObjects

Zabbix · Zabbix

The CUser.addRelatedObjects function in the Zabbix frontend contains an SQL injection reachable through the CUser.get API call. Any account with API access, including the default non-admin User role, can trigger it, so the flaw exposes the backend database to a low-privileged authenticated user.

9.9 CVSS 3.1 Critical EPSS 79% · top 0.4% CWE-89 · SQL injection
9.9CVSS 3.1 base score
79%EPSS exploitation probability, 30 days
NoNot in CISA KEV
1Affected product versions listed by NVD
1References
17 Jun 2026Last modified by NVD

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.

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

Automated analysis

Generated by VULONE's analysis model from the NVD record, CISA KEV and EPSS data on 18 September 2026. Confidence: high.

critical priorityCVSS 9.9 with network reachability, low-privilege authentication, scope change and high EPSS make this a top remediation priority.

What it is

The CUser.addRelatedObjects function in the Zabbix frontend contains an SQL injection reachable through the CUser.get API call. Any account with API access, including the default non-admin User role, can trigger it, so the flaw exposes the backend database to a low-privileged authenticated user.

Impact

An attacker with a basic API-enabled account can inject SQL to read or alter database contents, and the CVSS scope change plus high confidentiality, integrity and availability ratings indicate potential compromise beyond the frontend component.

Attack surface

Reached over the network through the Zabbix frontend API, specifically the CUser.get call. Authentication is required but only at a low privilege level; no user interaction is needed per the CVSS vector.

Exploitation

Not listed in CISA KEV and no public exploit references are tagged, but EPSS is very high at 0.787 (99.6th percentile), indicating strong likelihood of exploitation activity.

What to do

  • Apply the vendor fix referenced in Zabbix advisory ZBX-25623 as the first action.
  • Restrict API access to only accounts that genuinely require it and review role assignments.
  • Audit non-admin and default User role accounts, disabling or removing unused ones.
  • Monitor and rate-limit API calls to CUser.get from low-privileged accounts.
  • Place the Zabbix frontend behind access controls and network segmentation to limit exposure.

Detection

  • Search frontend and web server logs for anomalous CUser.get requests, especially from non-admin accounts.
  • Look for SQL syntax, UNION, or comment sequences in API request parameters.
  • Alert on database errors or unusual query patterns originating from the Zabbix frontend.
  • Baseline normal API usage per account and flag deviations in call volume or parameters.

This assessment is produced automatically and is not human-reviewed. Verify against the vendor advisory before acting on it.

Affected products

1 vulnerable configurations from NVD's CPE data, grouped by vendor and product.

References

LinkTags
https://support.zabbix.com/browse/ZBX-25623 Vendor Advisory

Track CVE-2024-42327 inside VULONE

Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.

Start free Open in platform

Related vulnerabilities

Same products first, then exploited flaws of the same weakness class.

9.8CVE-2022-23131Zabbix Frontend SAML SSO authentication bypass via session spoofingZabbix Frontend fails to verify the user login stored in the session when SAML SSO authentication is enabled, allowing session data to be modified. A…KEVEPSS 96%analysed5.3CVE-2022-23134Zabbix Frontend setup.php improper access control allows unauthenticated config changeAfter initial setup, some steps of Zabbix Frontend's setup.php remain reachable by unauthenticated users rather than only super-administrators. An at…KEVEPSS 95%analysed10.0CVE-2007-0640Zabbix vulnerabilityBuffer overflow in ZABBIX before 1.1.5 has unknown impact and attack vectors related to "SNMP IP addresses."EPSS 2.0%9.8CVE-2022-43516Microsoft windows firewall vulnerabilityA Firewall Rule which allows all incoming TCP connections to all programs from any source and to all ports is created in Windows Firewall after Zabbi…EPSS 0.95%9.8CVE-2020-11800Zabbix vulnerabilityZabbix Server 2.2.x and 3.0.x before 3.0.31, and 3.2 allows remote attackers to execute arbitrary code.EPSS 9.2%9.8CVE-2013-3738Zabbix improper input validation vulnerabilityA File Inclusion vulnerability exists in Zabbix 2.0.6 due to inadequate sanitization of request strings in CGI scripts, which could let a remote mali…EPSS 3.1%9.8CVE-2013-5743Zabbix SQL injection in multiple componentsZabbix versions 1.8.x before 1.8.18rc1, 2.0.x before 2.0.9rc1, and 2.1.x before 2.1.7 contain multiple SQL injection vulnerabilities. The record does…EPSS 80%analysed9.8CVE-2014-3005Zabbix xml external entity (xxe) vulnerabilityXML external entity (XXE) vulnerability in Zabbix 1.8.x before 1.8.21rc1, 2.0.x before 2.0.13rc1, 2.2.x before 2.2.5rc1, and 2.3.x before 2.3.2 allow…EPSS 5.2%

Source: NIST National Vulnerability Database (record CVE-2024-42327), CISA KEV, FIRST EPSS (scores of 2026-09-26). This page is refreshed as NVD updates the record.