CVE-2024-23108

CRITICALNVD 10.010.0
EchelonGraph scoreMEDIUM confidence

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

Score 10.0 from GitHub Security Advisory (severity: CRITICAL) published 2024-02-05. NVD baseline CVSS 10.0; 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-20633 (ENISA EUVD) · GHSA-chj3-8q43-rcc8 (GitHub Security Advisories)Source: ENISA EUVD

10.0EG
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 80%
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 80%CVSS: 10.0Exploit: Public PoCExposed services: Not assessed

Please upgrade to FortiSIEM version 7.1.2 or above (from the CVE record's solution, Fortinet, Inc.) — apply it.

An improper neutralization of special elements used in an os command ('os command injection') vulnerability in Fortinet allows attacker to execute unauthorized code or commands via via crafted API requests.

CVSS v3
10.0
EG Score
10.0CRITICALmedium confidence
EG Risk
92
EG Risk 92/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)
Severity100% × 45%
Impact severity (EG Severity): CVSS 10.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation80% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (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 yes (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: Please upgrade to FortiSIEM version 7.1.2 or above (from the CVE record's solution, Fortinet, Inc.). Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
80%
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 (10.0): severity, escalated by confirmed exploitation. This CVE's 10.0 is its impact severity (EG Severity), not escalated.

EG Severity
10.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
80% 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: 3 days if the affected system is publicly exposed; 60 days 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.

Please upgrade to FortiSIEM version 7.1.2 or above (from the CVE record's solution, Fortinet, Inc.). 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 yes (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)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

February 5, 2024

Last Modified

January 14, 2026

Advisory Details (2)

Auto-updated Nov 1, 2026
Fix named in the CVE record's solution (Fortinet, Inc.).
Web page

GitHub - horizon3ai/CVE-2024-23108: CVE-2024-23108: Fortinet FortiSIEM Unauthenticated 2nd Order Command Injection · GitHub

https://github.com/horizon3ai/CVE-2024-23108
Web page

PSIRT | FortiGuard Labs

https://fortiguard.com/psirt/FG-IR-23-130

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 131 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 32 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Publicly available exploits

(3 references)

Public exploit code is referenced for this CVE (2 GitHub PoCs), as is 1 Nuclei detection template. A detection template checks whether a system is affected; it is not necessarily exploit code. Defenders should treat patch urgency accordingly.

  • Nucleinetwork/cves/2024/CVE-2024-23108.yaml
    Published Oct 29, 2025

    Fortinet FortiSIEM - OS Command Injection

    Open source ↗
  • GitHub PoChitem/CVE-2024-23108
    Published May 28, 2024

    POC iteration for CVE-2024-23108 which can use -l for list input

    Open source ↗
  • GitHub PoChorizon3ai/CVE-2024-23108
    Published May 20, 2024

    CVE-2024-23108: Fortinet FortiSIEM Unauthenticated 2nd Order Command Injection

    Open source ↗

Frequently asked(5)

What is CVE-2024-23108?
CVE-2024-23108 is a critical-severity vulnerability; its CVE record was published on February 5, 2024. An improper neutralization of special elements used in an os command ('os command injection') vulnerability in Fortinet allows attacker to execute unauthorized code or commands via via crafted API requests.
When was the CVE record for CVE-2024-23108 published?
The CVE record for CVE-2024-23108 was published on February 5, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of January 14, 2026; the record at its source may have been updated since.
Is CVE-2024-23108 actively exploited?
CVE-2024-23108 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 80% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-23108?
CVE-2024-23108 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2024-23108?
The CVE record's solution for CVE-2024-23108, written by its CNA Fortinet, Inc., names the fix: "Please upgrade to FortiSIEM version 7.1.2 or above".

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2024-23108?

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