CVE-2024-22120

CRITICALNVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2024-05-17. NVD baseline CVSS 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Weaponized
9.1EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 77%
  • Public exploit code is available (ssvc poc, epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 77%CVSS: 9.1Exploit: ssvc poc · epss top5pct · epss high · public exploitExposed: 0

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

Zabbix server can perform command execution for configured scripts. After command is executed, audit entry is added to "Audit Log". Due to "clientip" field is not sanitized, it is possible to injection SQL into "clientip" and exploit time based blind SQL injection.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
72(Track*)
EG Risk 72/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
Severity91% × 45%
Exploitation77% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
77%
EPSS %ILE
99%
KEV
Not listed

Published

May 17, 2024

Last Modified

October 8, 2025

Advisory Details (1)

Auto-updated Aug 1, 2026
No patch confirmed yet.
generic

Loading...

https://support.zabbix.com/browse/ZBX-24505

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 1× in last 7d / 21× 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-05 19:15 UTCEPSS rescore
  2. 2026-08-01 02:42 UTCOSV refresh
  3. 2026-07-30 16:26 UTCEPSS rescore
  4. 2026-07-30 01:29 UTCEPSS rescore
  5. 2026-07-26 14:53 UTCEPSS rescore
  6. 2026-07-25 14:16 UTCEPSS rescore
  7. 2026-07-24 14:16 UTCEPSS rescore
  8. 2026-07-23 02:33 UTCEG score recompute
  9. 2026-07-22 23:20 UTCEG score recompute
  10. 2026-07-22 14:07 UTCEPSS rescore
  11. 2026-07-20 17:06 UTCEPSS rescore
  12. 2026-07-19 14:30 UTCEPSS rescore
  13. 2026-07-19 14:30 UTCEPSS rescore
  14. 2026-07-15 16:56 UTCEPSS rescore
  15. 2026-07-15 16:56 UTCEPSS rescore
  16. 2026-07-15 01:59 UTCEPSS rescore
  17. 2026-07-15 01:59 UTCEPSS rescore
  18. 2026-07-14 09:55 UTCOSV refresh
  19. 2026-07-13 22:28 UTCEPSS rescore
  20. 2026-07-12 05:45 UTCEPSS rescore
  21. 2026-07-11 08:26 UTCEPSS rescore
  22. 2026-07-07 13:45 UTCEPSS rescore
  23. 2026-07-07 13:45 UTCEPSS rescore
  24. 2026-07-05 02:29 UTCEPSS rescore
  25. 2026-07-01 15:05 UTCEPSS rescore
Show 45 more
  1. 2026-06-30 23:21 UTCEPSS rescore
  2. 2026-06-30 23:21 UTCEPSS rescore
  3. 2026-06-28 14:06 UTCEPSS rescore
  4. 2026-06-28 14:06 UTCEPSS rescore
  5. 2026-06-28 04:55 UTCEPSS rescore
  6. 2026-06-28 04:55 UTCEPSS rescore
  7. 2026-06-27 03:07 UTCEPSS rescore
  8. 2026-06-27 03:07 UTCEPSS rescore
  9. 2026-06-26 10:39 UTCOSV refresh
  10. 2026-06-25 13:48 UTCEPSS rescore
  11. 2026-06-25 13:48 UTCEPSS rescore
  12. 2026-06-24 14:04 UTCEPSS rescore
  13. 2026-06-24 14:04 UTCEPSS rescore
  14. 2026-06-23 21:32 UTCEPSS rescore
  15. 2026-06-23 21:32 UTCEPSS rescore
  16. 2026-06-22 14:24 UTCEPSS rescore
  17. 2026-06-22 14:24 UTCEPSS rescore
  18. 2026-06-21 01:58 UTCEPSS rescore
  19. 2026-06-21 01:58 UTCEPSS rescore
  20. 2026-06-17 17:52 UTCEPSS rescore
  21. 2026-06-17 17:52 UTCEPSS rescore
  22. 2026-06-16 17:51 UTCEPSS rescore
  23. 2026-06-16 17:51 UTCEPSS rescore
  24. 2026-06-15 17:47 UTCEPSS rescore
  25. 2026-06-12 23:11 UTCEPSS rescore
  26. 2026-06-10 22:17 UTCEPSS rescore
  27. 2026-06-10 13:21 UTCEPSS rescore
  28. 2026-06-10 13:21 UTCEPSS rescore
  29. 2026-06-08 17:41 UTCOSV refresh
  30. 2026-06-08 14:16 UTCEPSS rescore
  31. 2026-06-08 14:16 UTCEPSS rescore
  32. 2026-06-06 13:46 UTCEPSS rescore
  33. 2026-06-06 13:46 UTCEPSS rescore
  34. 2026-06-05 22:46 UTCEPSS rescore
  35. 2026-06-05 22:46 UTCEPSS rescore
  36. 2026-06-04 13:11 UTCEPSS rescore
  37. 2026-06-04 13:11 UTCEPSS rescore
  38. 2026-06-04 13:11 UTCEPSS rescore
  39. 2026-05-29 13:43 UTCEPSS rescore
  40. 2026-05-29 13:43 UTCEPSS rescore
  41. 2026-05-28 13:44 UTCEPSS rescore
  42. 2026-05-28 13:44 UTCEPSS rescore
  43. 2026-05-28 13:44 UTCEPSS rescore
  44. 2026-05-24 01:55 UTCEG score recompute
  45. 2026-05-24 01:55 UTCGHSA enrichment

Publicly available exploits

(3 references)

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

  • GitHub PoCg4nkd/CVE-2024-22120-RCE-with-gopher
    First seen Aug 14, 2024

    This exploit was created to exploit an XXE (XML External Entity). Through it, I read the backend code of the web service and found an endpoint where I could use gopher to make internal requests on Zabbix vulnerable to RCE.

    Open source ↗
  • GitHub PoCisPique/CVE-2024-22120-RCE-with-gopher
    First seen Aug 13, 2024

    This is my exploit for CVE-2024-22120, which involves an SSRF vulnerability inside an XXE with a Gopher payload.

    Open source ↗
  • GitHub PoCW01fh4cker/CVE-2024-22120-RCE
    First seen May 20, 2024

    Time Based SQL Injection in Zabbix Server Audit Log --> RCE

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2024-22120?
CVE-2024-22120 is a critical vulnerability published on May 17, 2024. Zabbix server can perform command execution for configured scripts. After command is executed, audit entry is added to "Audit Log". Due to "clientip" field is not sanitized, it is possible to injection SQL into "clientip" and exploit time based blind SQL injection.
When was CVE-2024-22120 disclosed?
CVE-2024-22120 was first published in the National Vulnerability Database on May 17, 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-22120 actively exploited?
CVE-2024-22120 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 77% probability of exploitation in the next 30 days, which ranks it in the top 0.5% of all scored CVEs.
What is the CVSS score of CVE-2024-22120?
CVE-2024-22120 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2024-22120?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-22120, 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-22120

Explore →

Is Your Infrastructure Affected by CVE-2024-22120?

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

Start Free Scan →Browse All CVEs