CVE-2024-42327

CRITICALNVD 9.99.9
EchelonGraph scoreMEDIUM confidence

Score 9.9 from GitHub Security Advisory (severity: CRITICAL) published 2024-11-27. NVD baseline CVSS 9.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
9.9EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 79%
CISA-KEV: Not listedEPSS PROB: 79%CVSS: 9.9Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 v3
9.9
EG Score
9.9(medium)
EG Risk
76(Track)
EG Risk 76/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity99% × 45%
Exploitation79% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
79%
EPSS %ILE
100%
KEV
Not listed

Published

November 27, 2024

Last Modified

October 8, 2025

Advisory Details (1)

Auto-updated Aug 3, 2026
No patch confirmed yet.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 2× in last 7d / 20× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-07 16:25 UTCEPSS rescore
  2. 2026-08-03 10:34 UTCEPSS rescore
  3. 2026-07-31 10:12 UTCOSV refresh
  4. 2026-07-30 01:29 UTCEPSS rescore
  5. 2026-07-28 15:34 UTCEPSS rescore
  6. 2026-07-26 14:53 UTCEPSS rescore
  7. 2026-07-26 14:53 UTCEPSS rescore
  8. 2026-07-24 14:16 UTCEPSS rescore
  9. 2026-07-23 14:17 UTCEPSS rescore
  10. 2026-07-23 02:39 UTCEG score recompute
  11. 2026-07-22 14:07 UTCEPSS rescore
  12. 2026-07-21 15:23 UTCEPSS rescore
  13. 2026-07-21 15:23 UTCEPSS rescore
  14. 2026-07-20 17:06 UTCEPSS rescore
  15. 2026-07-16 17:02 UTCEPSS rescore
  16. 2026-07-15 16:56 UTCEPSS rescore
  17. 2026-07-15 16:56 UTCEPSS rescore
  18. 2026-07-13 22:29 UTCEPSS rescore
  19. 2026-07-13 17:38 UTCOSV refresh
  20. 2026-07-11 08:26 UTCEPSS rescore
  21. 2026-07-08 15:14 UTCEPSS rescore
  22. 2026-07-01 15:05 UTCEPSS rescore
  23. 2026-06-25 15:16 UTCOSV refresh
  24. 2026-06-25 13:49 UTCEPSS rescore
  25. 2026-06-23 21:32 UTCEPSS rescore
Show 28 more
  1. 2026-06-23 21:32 UTCEPSS rescore
  2. 2026-06-21 14:55 UTCEPSS rescore
  3. 2026-06-17 17:52 UTCEPSS rescore
  4. 2026-06-16 17:52 UTCEPSS rescore
  5. 2026-06-16 17:52 UTCEPSS rescore
  6. 2026-06-15 17:47 UTCEPSS rescore
  7. 2026-06-13 22:59 UTCEPSS rescore
  8. 2026-06-13 22:59 UTCEPSS rescore
  9. 2026-06-13 22:59 UTCEPSS rescore
  10. 2026-06-12 23:11 UTCEPSS rescore
  11. 2026-06-12 23:11 UTCEPSS rescore
  12. 2026-06-10 22:18 UTCEPSS rescore
  13. 2026-06-08 05:28 UTCOSV refresh
  14. 2026-06-06 13:46 UTCEPSS rescore
  15. 2026-06-06 13:46 UTCEPSS rescore
  16. 2026-06-05 22:46 UTCEPSS rescore
  17. 2026-06-05 22:46 UTCEPSS rescore
  18. 2026-06-02 20:12 UTCEPSS rescore
  19. 2026-06-02 20:12 UTCEPSS rescore
  20. 2026-05-28 13:44 UTCEPSS rescore
  21. 2026-05-28 13:44 UTCEPSS rescore
  22. 2026-05-26 13:43 UTCEPSS rescore
  23. 2026-05-26 13:43 UTCEPSS rescore
  24. 2026-05-26 07:18 UTCEPSS rescore
  25. 2026-05-26 07:18 UTCEPSS rescore
  26. 2026-05-26 07:18 UTCEPSS rescore
  27. 2026-05-23 17:16 UTCEG score recompute
  28. 2026-05-23 17:16 UTCGHSA enrichment

Publicly available exploits

(6 references)

Working exploit code is in the public domain (5 GitHub PoCs) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-52230
    First seen Apr 16, 2025

    Zabbix 7.0.0 - SQL Injection

    Open source ↗
  • GitHub PoCgodylockz/CVE-2024-42327
    First seen Feb 16, 2025

    POC for CVE-2024-42327: Zabbix Privilege Escalation -> RCE

    Open source ↗
  • GitHub PoCwatchdog1337/CVE-2024-42327_Zabbix_SQLI
    First seen Dec 7, 2024

    POC for CVE-2024-42327, an authenticated SQL Injection in Zabbix through the user.get API Method

    Open source ↗
  • GitHub PoCdepers-rus/CVE-2024-42327
    First seen Dec 6, 2024
    Open source ↗
  • GitHub PoCcompr00t/CVE-2024-42327
    First seen Dec 3, 2024

    PoC for CVE-2024-42327 / ZBX-25623

    Open source ↗
  • GitHub PoCaramosf/cve-2024-42327
    First seen Dec 1, 2024

    cve-2024-42327 ZBX-25623

    Open source ↗

Frequently asked(5)

What is CVE-2024-42327?
CVE-2024-42327 is a critical vulnerability published on November 27, 2024. 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…
When was CVE-2024-42327 disclosed?
CVE-2024-42327 was first published in the National Vulnerability Database on November 27, 2024, with the most recent update on October 8, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-42327 actively exploited?
CVE-2024-42327 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 79% probability of exploitation in the next 30 days, which ranks it in the top 0.4% of all scored CVEs.
What is the CVSS score of CVE-2024-42327?
CVE-2024-42327 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2024-42327?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-42327, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2024-42327

Explore →

Is Your Infrastructure Affected by CVE-2024-42327?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.