CVE-2024-14037

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-02. A secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated
9.8EG
EchelonGraph verdictPlan mitigationRemediate 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: 1.3%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

Redsea Cloud eHR contains an arbitrary file upload vulnerability that allows unauthenticated attackers to achieve remote code execution by uploading malicious files through the PtFjk.mob servlet endpoint. Attackers can submit a multipart POST request with a JSP webshell disguised using a spoofed image/jpeg Content-Type to bypass the absence of extension and MIME type validation, with the uploaded file stored at a predictable path under the uploadfile directory and executed directly by the web server. Exploitation evidence was first observed by the Shadowserver Foundation on 2024-11-03 (UTC).

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 intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
The EG Score, 9.8 of 10.
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, 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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
1.3%
EPSS %ILE
69th
KEV
Not listed

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

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

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.

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

July 2, 2026

Last Modified

October 2, 2026

Advisory Details (4)

Auto-updated Oct 9, 2026
No fix on record yet.
Web page

Redsea Cloud eHR Unauthenticated File Upload RCE via PtFjk.mob | Advisories | VulnCheck

https://www.vulncheck.com/advisories/redsea-cloud-ehr-unauthenticated-file-upload-rce-via-ptfjk-mob
Web page

Home - Red Sea Cloud

https://redseacloud.com/
Web page

红海云-EHR系统-任意文件上传 | CN-SEC 中文网

https://cn-sec.com/archives/3003231.html
Web page

【1day】红海云EHR任意文件上传漏洞复现 | CN-SEC 中文网

https://cn-sec.com/archives/2734791.html

Vendor Advisories for CVE-2024-14037(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 44× 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 424 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 328 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2024-14037?
CVE-2024-14037 is a critical-severity vulnerability; its CVE record was published on July 2, 2026. Redsea Cloud eHR contains an arbitrary file upload vulnerability that allows unauthenticated attackers to achieve remote code execution by uploading malicious files through the PtFjk.mob servlet endpoint. Attackers can submit a multipart POST request with a JSP webshell disguised using a spoofed…
When was CVE-2024-14037 made public?
CVE-2024-14037 was made public on May 14, 2024: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on July 2, 2026. EchelonGraph's copy of the record carries a last-modified date of October 2, 2026; the record at its source may have been updated since.
Is CVE-2024-14037 actively exploited?
CVE-2024-14037 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.3% probability of exploitation in the next 30 days (69th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-14037?
CVE-2024-14037 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2024-14037?
No fix for CVE-2024-14037 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2024-14037 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2024-14037?

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

Book a Demo →Browse All CVEs