CVE-2024-11311

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

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

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

Also known asEUVD-2024-33722 (ENISA EUVD) · GHSA-qj3w-6895-r5mf (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).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.4%CVSS: 9.8Exploit: None knownExposed services: Not assessed

Update to version 6.4 or later (from the CVE record's solution, TWCERT/CC) — apply it.

The DVC from TRCore has a Path Traversal vulnerability and does not restrict the types of uploaded files. This allows unauthenticated remote attackers to upload arbitrary files to any directory, leading to arbitrary code execution by uploading webshells.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
60
EG Risk 60/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.
Exploitation1.4% × 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 or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (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: Update to version 6.4 or later (from the CVE record's solution, TWCERT/CC). Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
1.4%
EPSS %ILE
72nd
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.GitHub Security Advisory CVSS
EG Likelihood
1.4% 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: 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 or medium mission impact; Attend at high (mission-essential systems).

Update to version 6.4 or later (from the CVE record's solution, TWCERT/CC). Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (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

November 18, 2024

Last Modified

November 20, 2024

Advisory Details (2)

Auto-updated Oct 7, 2026
Fix named in the CVE record's solution (TWCERT/CC). Sources: cert.
CERT

統睿科技DVC文件保險系統 - Arbitrary File Upload through Path Traversal-TWCERT/CC台灣電腦網路危機處理暨協調中心|企業資安通報協處|資安情資分享|漏洞通報|資安聯盟|資安電子報

https://www.twcert.org.tw/tw/cp-132-8246-d462a-1.html
CERT

TRCore DVC - Arbitrary File Upload through Path Traversal-TWCERT/CC Taiwan Computer Emergency Response Team/Coordination Center

https://www.twcert.org.tw/en/cp-139-8247-83457-2.html

Weakness Classification(3)

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

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

Frequently asked(5)

What is CVE-2024-11311?
CVE-2024-11311 is a critical-severity vulnerability; its CVE record was published on November 18, 2024. The DVC from TRCore has a Path Traversal vulnerability and does not restrict the types of uploaded files. This allows unauthenticated remote attackers to upload arbitrary files to any directory, leading to arbitrary code execution by uploading webshells.
When was CVE-2024-11311 made public?
CVE-2024-11311 was made public on November 18, 2024: that is the date its CVE record's CNA, TWCERT/CC, gives for when the vulnerability was made public. The CVE record itself was published on November 18, 2024. EchelonGraph's copy of the record carries a last-modified date of November 20, 2024; the record at its source may have been updated since.
Is CVE-2024-11311 actively exploited?
CVE-2024-11311 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.4% probability of exploitation in the next 30 days (72nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-11311?
CVE-2024-11311 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2024-11311?
The CVE record's solution for CVE-2024-11311, written by its CNA TWCERT/CC, names the fix: "Update to version 6.4 or later."

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2024-11311?

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