CVE-2024-13061

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-12-31. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2024-51314 (ENISA EUVD) · GHSA-2vmj-9h29-92pm (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.3%CVSS: 9.8Exploit: None knownExposed services: Not assessed

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

The Electronic Official Document Management System from 2100 Technology has an Authentication Bypass vulnerability. Although the product enforces an IP whitelist for the API used to query user tokens, unauthenticated remote attackers can still deceive the server to obtain tokens of arbitrary users, which can then be used to log into the system.

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.3% × 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 5.0.86.9 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.3%
EPSS %ILE
70th
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.3% 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 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 5.0.86.9 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

December 31, 2024

Last Modified

April 15, 2026

Advisory Details (4)

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

二一零零科技電子公文檔案資訊管理系統 - Authentication Bypass-TWCERT/CC台灣電腦網路危機處理暨協調中心|企業資安通報協處|資安情資分享|漏洞通報|資安聯盟|資安電子報

https://www.twcert.org.tw/tw/cp-132-8339-570fa-1.html
CERT

2100 Technology Electronic Official Document Management System - Authentication Bypass-TWCERT/CC Taiwan Computer Emergency Response Team/Coordination Center

https://www.twcert.org.tw/en/cp-139-8340-d8b16-2.html
Web page

中華資安國際發現CVE弱點,國內某公文系統存在驗證機制失效 弱點,可能導致敏感資料洩漏|中華資安國際 CHT Security Co., Ltd.

https://www.chtsecurity.com/news/ade9e9af-61d0-4e3c-8aa0-e8524ee2cfbc
Web page

CHT Security Red Team Discovered a Vulnerability in a Well-Known Official Document Management System.|中華資安國際 CHT Security Co., Ltd.

https://www.chtsecurity.com/news/255984da-6630-4e25-ba9b-5ce6933935a6

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 19× in last 7d / 71× 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 96 of 261 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. 4 repeat rows among the latest 100 are merged into the row they repeat. The 165 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2024-13061?
CVE-2024-13061 is a critical-severity vulnerability; its CVE record was published on December 31, 2024. The Electronic Official Document Management System from 2100 Technology has an Authentication Bypass vulnerability. Although the product enforces an IP whitelist for the API used to query user tokens, unauthenticated remote attackers can still deceive the server to obtain tokens of arbitrary users,…
When was CVE-2024-13061 made public?
CVE-2024-13061 was made public on December 31, 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 December 31, 2024. EchelonGraph's copy of the record carries a last-modified date of April 15, 2026; the record at its source may have been updated since.
Is CVE-2024-13061 actively exploited?
CVE-2024-13061 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.3% probability of exploitation in the next 30 days (70th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-13061?
CVE-2024-13061 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2024-13061?
The CVE record's solution for CVE-2024-13061, written by its CNA TWCERT/CC, names the fix: "Update to version 5.0.86.9 or later."

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2024-13061?

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