CVE-2024-22120

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

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, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekWeaponized

Also known asEUVD-2024-19716 (ENISA EUVD) · GHSA-625f-58w6-wj9f (GitHub Security Advisories)Source: ENISA EUVD

9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High exploitation likelihood — EPSS 77%
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 77%CVSS: 9.1Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

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.1CRITICALmedium confidence
EG Risk
72
EG Risk 72/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation77% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
77%
EPSS %ILE
99th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
77% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 17, 2024

Last Modified

October 8, 2025

Advisory Details (1)

Auto-updated Aug 1, 2026
Patch available.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
zabbix1:6.0.14+dfsg-1 ... 1:7.0.9+dfsg-1~bpo12+1 (28 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
zabbix—
  • every version up to 1:6.0.29+dfsg-1: fixed in 1:6.0.29+dfsg-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
zabbix—
  • every version up to 1:6.0.29+dfsg-1: fixed in 1:6.0.29+dfsg-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 18× in last 7d / 64× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 163 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 64 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 01:27 UTCEG score recompute
  2. 2026-11-02 01:27 UTCGHSA enrichmentGHSA-625f-58w6-wj9f · GitHub severity CRITICAL · GitHub CVSS 9.1
  3. 2026-11-01 01:44 UTCEG score recompute
  4. 2026-11-01 01:44 UTCGHSA enrichmentGHSA-625f-58w6-wj9f · GitHub severity CRITICAL · GitHub CVSS 9.1
  5. 2026-10-31 16:30 UTCEPSS rescoreEPSS 77% · 99th percentile
  6. 2026-10-31 02:00 UTCEG score recompute
  7. 2026-10-31 02:00 UTCGHSA enrichmentGHSA-625f-58w6-wj9f · GitHub severity CRITICAL · GitHub CVSS 9.1
  8. 2026-10-30 16:31 UTCEPSS rescoreEPSS 77% · 99th percentile
  9. 2026-10-30 02:17 UTCEG score recompute
  10. 2026-10-30 02:17 UTCGHSA enrichmentGHSA-625f-58w6-wj9f · GitHub severity CRITICAL · GitHub CVSS 9.1
  11. 2026-10-29 02:34 UTCEG score recompute
  12. 2026-10-29 02:33 UTCGHSA enrichmentGHSA-625f-58w6-wj9f · GitHub severity CRITICAL · GitHub CVSS 9.1
  13. 2026-10-28 16:29 UTCEPSS rescoreEPSS 77% · 99th percentile
  14. 2026-10-28 02:47 UTCEG score recompute
  15. 2026-10-28 02:47 UTCGHSA enrichmentGHSA-625f-58w6-wj9f · GitHub severity CRITICAL · GitHub CVSS 9.1
  16. 2026-10-27 16:29 UTCEPSS rescoreEPSS 77% · 99th percentile
  17. 2026-10-27 02:58 UTCEG score recompute
  18. 2026-10-27 02:58 UTCGHSA enrichmentGHSA-625f-58w6-wj9f · GitHub severity CRITICAL · GitHub CVSS 9.1
  19. 2026-10-26 16:29 UTCEPSS rescoreEPSS 77% · 99th percentile
  20. 2026-10-25 23:12 UTCGHSA enrichmentGHSA-625f-58w6-wj9f · GitHub severity CRITICAL · GitHub CVSS 9.1
  21. 2026-10-25 17:18 UTCEG score recompute
  22. 2026-10-25 16:30 UTCEPSS rescoreEPSS 77% · 99th percentile
  23. 2026-10-24 23:28 UTCEG score recompute
  24. 2026-10-24 23:28 UTCGHSA enrichmentGHSA-625f-58w6-wj9f · GitHub severity CRITICAL · GitHub CVSS 9.1
  25. 2026-10-24 16:30 UTCEPSS rescoreEPSS 77% · 99th percentile
Show 74 more
  1. 2026-10-23 23:45 UTCEG score recompute
  2. 2026-10-23 23:45 UTCGHSA enrichmentGHSA-625f-58w6-wj9f · GitHub severity CRITICAL · GitHub CVSS 9.1
  3. 2026-10-23 00:01 UTCEG score recompute
  4. 2026-10-23 00:01 UTCGHSA enrichmentGHSA-625f-58w6-wj9f · GitHub severity CRITICAL · GitHub CVSS 9.1
  5. 2026-10-22 16:31 UTCEPSS rescoreEPSS 77% · 99th percentile
  6. 2026-10-22 00:17 UTCEG score recompute
  7. 2026-10-22 00:16 UTCGHSA enrichmentGHSA-625f-58w6-wj9f · GitHub severity CRITICAL · GitHub CVSS 9.1
  8. 2026-10-21 16:29 UTCEPSS rescoreEPSS 77% · 99th percentile
  9. 2026-10-21 00:30 UTCEG score recompute
  10. 2026-10-21 00:30 UTCGHSA enrichmentGHSA-625f-58w6-wj9f · GitHub severity CRITICAL · GitHub CVSS 9.1
  11. 2026-10-20 16:30 UTCEPSS rescoreEPSS 77% · 99th percentile
  12. 2026-10-20 00:43 UTCEG score recompute
  13. 2026-10-20 00:43 UTCGHSA enrichmentGHSA-625f-58w6-wj9f · GitHub severity CRITICAL · GitHub CVSS 9.1
  14. 2026-10-18 23:41 UTCEG score recompute
  15. 2026-10-18 23:41 UTCGHSA enrichmentGHSA-625f-58w6-wj9f · GitHub severity CRITICAL · GitHub CVSS 9.1
  16. 2026-10-18 07:27 UTCEG score recompute
  17. 2026-10-17 23:56 UTCEG score recompute
  18. 2026-10-17 23:56 UTCGHSA enrichmentGHSA-625f-58w6-wj9f · GitHub severity CRITICAL · GitHub CVSS 9.1
  19. 2026-10-17 00:12 UTCEG score recompute
  20. 2026-10-17 00:11 UTCGHSA enrichmentGHSA-625f-58w6-wj9f · GitHub severity CRITICAL · GitHub CVSS 9.1
  21. 2026-10-16 16:36 UTCEPSS rescoreEPSS 77% · 99th percentile
  22. 2026-10-15 21:17 UTCEG score recompute
  23. 2026-10-15 21:17 UTCGHSA enrichmentGHSA-625f-58w6-wj9f · GitHub severity CRITICAL · GitHub CVSS 9.1
  24. 2026-10-15 16:29 UTCEPSS rescoreEPSS 77% · 99th percentile
  25. 2026-10-14 16:30 UTCEPSS rescoreEPSS 77% · 99th percentile
  26. 2026-10-14 15:18 UTCEG score recompute
  27. 2026-10-14 15:18 UTCGHSA enrichmentGHSA-625f-58w6-wj9f · GitHub severity CRITICAL · GitHub CVSS 9.1
  28. 2026-10-13 16:30 UTCEPSS rescoreEPSS 77% · 99th percentile
  29. 2026-10-13 14:44 UTCEG score recompute
  30. 2026-10-13 14:44 UTCGHSA enrichmentGHSA-625f-58w6-wj9f · GitHub severity CRITICAL · GitHub CVSS 9.1
  31. 2026-10-12 14:59 UTCEG score recompute
  32. 2026-10-12 14:59 UTCGHSA enrichmentGHSA-625f-58w6-wj9f · GitHub severity CRITICAL · GitHub CVSS 9.1
  33. 2026-10-12 14:58 UTCGHSA enrichmentGHSA-625f-58w6-wj9f · GitHub severity CRITICAL · GitHub CVSS 9.1
  34. 2026-10-11 21:27 UTCEG score recompute
  35. 2026-10-11 16:21 UTCEG score recompute
  36. 2026-10-11 01:22 UTCOSV refresh
  37. 2026-10-10 19:58 UTCEPSS rescoreEPSS 77% · 99th percentile
  38. 2026-10-09 20:05 UTCEPSS rescoreEPSS 77% · 99th percentile
  39. 2026-10-07 23:46 UTCEPSS rescoreEPSS 77% · 99th percentile
  40. 2026-10-03 14:23 UTCEPSS rescoreEPSS 77% · 99th percentile
  41. 2026-10-01 19:48 UTCEPSS rescoreEPSS 77% · 99th percentile
  42. 2026-09-30 16:56 UTCEG score recompute
  43. 2026-09-24 14:01 UTCEPSS rescoreEPSS 77% · 99th percentile
  44. 2026-09-23 13:46 UTCEPSS rescoreEPSS 77% · 99th percentile
  45. 2026-09-21 12:49 UTCOSV refresh
  46. 2026-09-20 20:14 UTCEPSS rescoreEPSS 77% · 99th percentile
  47. 2026-09-16 14:06 UTCEPSS rescoreEPSS 77% · 99th percentile
  48. 2026-09-16 05:11 UTCEPSS rescoreEPSS 77% · 99th percentile
  49. 2026-09-13 16:45 UTCEPSS rescoreEPSS 77% · 99th percentile
  50. 2026-09-12 14:59 UTCEPSS rescoreEPSS 77% · 99th percentile
  51. 2026-09-11 09:34 UTCEPSS rescoreEPSS 77% · 99th percentile
  52. 2026-09-08 21:58 UTCEPSS rescoreEPSS 77% · 99th percentile
  53. 2026-09-06 13:46 UTCEPSS rescoreEPSS 77% · 99th percentile
  54. 2026-09-05 15:26 UTCEPSS rescoreEPSS 77% · 99th percentile
  55. 2026-09-02 14:10 UTCEPSS rescoreEPSS 77% · 99th percentile
  56. 2026-09-02 10:14 UTCOSV refresh
  57. 2026-08-30 19:15 UTCEPSS rescoreEPSS 77% · 99th percentile
  58. 2026-08-30 01:20 UTCEPSS rescoreEPSS 77% · 99th percentile
  59. 2026-08-28 21:39 UTCEPSS rescoreEPSS 77% · 99th percentile
  60. 2026-08-27 14:23 UTCEPSS rescoreEPSS 77% · 99th percentile
  61. 2026-08-25 13:47 UTCEPSS rescoreEPSS 77% · 99th percentile
  62. 2026-08-21 23:47 UTCEPSS rescoreEPSS 77% · 99th percentile
  63. 2026-08-19 17:02 UTCEPSS rescoreEPSS 77% · 99th percentile
  64. 2026-08-16 08:47 UTCOSV refresh
  65. 2026-08-16 02:12 UTCEPSS rescoreEPSS 77% · 99th percentile
  66. 2026-08-15 01:28 UTCEPSS rescoreEPSS 77% · 99th percentile
  67. 2026-08-12 13:49 UTCEPSS rescoreEPSS 77% · 99th percentile
  68. 2026-08-11 13:40 UTCEPSS rescoreEPSS 77% · 99th percentile
  69. 2026-08-05 19:15 UTCEPSS rescoreEPSS 77% · 99th percentile
  70. 2026-08-01 02:42 UTCOSV refresh
  71. 2026-07-30 16:26 UTCEPSS rescoreEPSS 77% · 99th percentile
  72. 2026-07-30 01:29 UTCEPSS rescoreEPSS 77% · 99th percentile
  73. 2026-07-26 14:53 UTCEPSS rescoreEPSS 77% · 99th percentile
  74. 2026-07-25 14:16 UTCEPSS rescoreEPSS 77% · 99th percentile

Publicly available exploits

(3 references)

Public exploit code is referenced for this CVE (3 GitHub PoCs). Defenders should treat patch urgency accordingly.

  • GitHub PoCg4nkd/CVE-2024-22120-RCE-with-gopher
    Published 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
    Published 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
    Published May 20, 2024

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

    Open source ↗

Frequently asked(5)

What is CVE-2024-22120?
CVE-2024-22120 is a critical-severity vulnerability; its CVE record was 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 made public?
CVE-2024-22120 was made public on May 17, 2024: that is the date its CVE record's CNA, Zabbix, gives for when the vulnerability was made public. The CVE record itself was published on May 17, 2024. EchelonGraph's copy of the record carries a last-modified date of October 8, 2025; the record at its source may have been updated since.
Is CVE-2024-22120 actively exploited?
CVE-2024-22120 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: CISA's SSVC data says a public PoC exists and its EPSS is 50% or more. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 77% probability of exploitation in the next 30 days (99th percentile of EPSS-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?
A fix for CVE-2024-22120 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.