CVE-2024-5982

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 31% (98th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 9.1 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2024-10-29) is not newer than that change (2024-11-14), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Elevated

Also known asEUVD-2024-47099 (ENISA EUVD) · GHSA-p6jm-98c6-m9x8 (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
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).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 31%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

A path traversal vulnerability exists in the latest version of gaizhenbiao/chuanhuchatgpt. The vulnerability arises from unsanitized input handling in multiple features, including user upload, directory creation, and template loading. Specifically, the load_chat_history function in modules/models/base_model.py allows arbitrary file uploads, potentially leading to remote code execution (RCE). The get_history_names function in utils.py permits arbitrary directory creation. Additionally, the load_template function in utils.py can be exploited to leak the first column of CSV files. These issues stem from improper sanitization of user inputs concatenated with directory paths using os.path.join.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
75
EG Risk 75/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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
31%
EPSS %ILE
98th
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.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
31% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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 or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 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 or medium mission impact; Attend at high (mission-essential systems).

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 yes (CISA Vulnrichment) · Technical impact partial (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; 60 days if it is not.

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

October 29, 2024

Last Modified

November 14, 2024

Advisory Details (2)

Auto-updated Oct 7, 2026
Patch available. Sources: github_commit.
Web page

huntr - The world's first bug bounty platform for AI/ML

https://huntr.com/bounties/5d5c5356-e893-44d1-b5ca-642aa05d96bb
GitHub commit Patch Available

commit 952fc8c3cbac (gaizhenbiao/chuanhuchatgpt)

Patch available: gaizhenbiao/chuanhuchatgpt 20240919-4 (contains commit 952fc8c3cbac)

https://github.com/gaizhenbiao/chuanhuchatgpt/commit/952fc8c3cbacead858311747cddd4bedcb4721d7

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 59× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 261 rows 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. None are among the latest 100 rows. The 161 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2024-5982?
CVE-2024-5982 is a critical-severity vulnerability; its CVE record was published on October 29, 2024. A path traversal vulnerability exists in the latest version of gaizhenbiao/chuanhuchatgpt. The vulnerability arises from unsanitized input handling in multiple features, including user upload, directory creation, and template loading. Specifically, the load_chat_history function in…
When was the CVE record for CVE-2024-5982 published?
The CVE record for CVE-2024-5982 was published on October 29, 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 November 14, 2024; the record at its source may have been updated since.
Is CVE-2024-5982 actively exploited?
CVE-2024-5982 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 31% probability of exploitation in the next 30 days (98th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-5982?
CVE-2024-5982 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2024-5982?
A fix for CVE-2024-5982 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2024-5982?

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