CVE-2024-0204

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-01-22. 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 weekWeaponized

Also known asEUVD-2024-16003 (ENISA EUVD) · GHSA-f8xf-39w2-mrc6 (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 exploitation likelihood — EPSS 95%
  • Public exploit code is available (Metasploit, other public proof-of-concept code)
CISA-KEV: Not listedEPSS PROB: 95%CVSS: 9.8Exploit: Metasploit · other public PoCExposed services: Not assessed

Upgrade to version 7.4.1 or higher (from the CVE record's solution, Fortra, LLC) — apply it.

Authentication bypass in Fortra's GoAnywhere MFT prior to 7.4.1 allows an unauthorized user to create an admin user via the administration portal.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
97
EG Risk 97/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.
Exploitation95% × 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: Upgrade to version 7.4.1 or higher (from the CVE record's solution, Fortra, LLC). Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
95%
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 (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
95% 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).

Upgrade to version 7.4.1 or higher (from the CVE record's solution, Fortra, LLC). 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

January 22, 2024

Last Modified

November 21, 2024

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 51× 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.

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. 9 repeat rows among the latest 91 are merged into the row they repeat.

  1. 2026-11-02 13:48 UTCEG score recompute
  2. 2026-11-02 13:48 UTCGHSA enrichmentGHSA-f8xf-39w2-mrc6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-11-01 14:05 UTCEG score recompute
  4. 2026-11-01 14:05 UTCGHSA enrichmentGHSA-f8xf-39w2-mrc6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  5. 2026-10-31 16:30 UTCEPSS rescoreEPSS 95% · 99th percentile
  6. 2026-10-31 14:22 UTCEG score recompute
  7. 2026-10-31 14:22 UTCGHSA enrichmentGHSA-f8xf-39w2-mrc6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  8. 2026-10-30 14:39 UTCEG score recompute
  9. 2026-10-30 14:39 UTCGHSA enrichmentGHSA-f8xf-39w2-mrc6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  10. 2026-10-29 14:58 UTCEG score recompute
  11. 2026-10-29 14:58 UTCGHSA enrichmentGHSA-f8xf-39w2-mrc6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-10-28 15:16 UTCEG score recompute
  13. 2026-10-28 15:16 UTCGHSA enrichmentGHSA-f8xf-39w2-mrc6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  14. 2026-10-27 15:34 UTCEG score recompute
  15. 2026-10-27 15:34 UTCGHSA enrichmentGHSA-f8xf-39w2-mrc6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-10-26 15:37 UTCEG score recompute
  17. 2026-10-26 15:37 UTCGHSA enrichmentGHSA-f8xf-39w2-mrc6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-10-25 16:30 UTCEPSS rescoreEPSS 95% · 99th percentile
  19. 2026-10-25 15:44 UTCEG score recompute
  20. 2026-10-25 15:44 UTCGHSA enrichmentGHSA-f8xf-39w2-mrc6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  21. 2026-10-24 15:58 UTCEG score recompute
  22. 2026-10-24 15:58 UTCGHSA enrichmentGHSA-f8xf-39w2-mrc6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  23. 2026-10-23 16:15 UTCEG score recompute
  24. 2026-10-23 16:15 UTCGHSA enrichmentGHSA-f8xf-39w2-mrc6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  25. 2026-10-22 16:30 UTCEG score recompute
Show 57 more
  1. 2026-10-22 16:30 UTCGHSA enrichmentGHSA-f8xf-39w2-mrc6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  2. 2026-10-21 16:29 UTCEPSS rescoreEPSS 95% · 99th percentile
  3. 2026-10-21 16:18 UTCGHSA enrichmentGHSA-f8xf-39w2-mrc6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-10-20 16:37 UTCEG score recompute
  5. 2026-10-20 16:36 UTCGHSA enrichmentGHSA-f8xf-39w2-mrc6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-10-19 16:47 UTCEG score recompute
  7. 2026-10-19 16:47 UTCGHSA enrichmentGHSA-f8xf-39w2-mrc6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  8. 2026-10-19 16:29 UTCEPSS rescoreEPSS 95% · 99th percentile
  9. 2026-10-18 16:44 UTCEG score recompute
  10. 2026-10-18 16:43 UTCGHSA enrichmentGHSA-f8xf-39w2-mrc6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  11. 2026-10-18 07:37 UTCEG score recompute
  12. 2026-10-18 00:06 UTCEG score recompute
  13. 2026-10-18 00:05 UTCGHSA enrichmentGHSA-f8xf-39w2-mrc6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  14. 2026-10-17 00:22 UTCEG score recompute
  15. 2026-10-17 00:21 UTCGHSA enrichmentGHSA-f8xf-39w2-mrc6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-10-15 23:53 UTCEG score recompute
  17. 2026-10-15 23:53 UTCGHSA enrichmentGHSA-f8xf-39w2-mrc6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-10-14 16:30 UTCEPSS rescoreEPSS 95% · 99th percentile
  19. 2026-10-14 15:48 UTCEG score recompute
  20. 2026-10-14 15:48 UTCGHSA enrichmentGHSA-f8xf-39w2-mrc6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  21. 2026-10-13 14:56 UTCEG score recompute
  22. 2026-10-13 14:55 UTCGHSA enrichmentGHSA-f8xf-39w2-mrc6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  23. 2026-10-12 15:12 UTCEG score recompute
  24. 2026-10-12 15:11 UTCGHSA enrichmentGHSA-f8xf-39w2-mrc6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  25. 2026-10-11 21:35 UTCEG score recompute
  26. 2026-10-04 23:20 UTCEPSS rescoreEPSS 95% · 99th percentile
  27. 2026-09-30 16:40 UTCEG score recompute
  28. 2026-09-28 13:49 UTCEPSS rescoreEPSS 95% · 99th percentile
  29. 2026-09-24 14:01 UTCEPSS rescoreEPSS 95% · 99th percentile
  30. 2026-09-18 19:26 UTCEPSS rescoreEPSS 95% · 99th percentile
  31. 2026-09-15 03:08 UTCEPSS rescoreEPSS 95% · 99th percentile
  32. 2026-09-06 13:46 UTCEPSS rescoreEPSS 95% · 99th percentile
  33. 2026-09-05 15:26 UTCEPSS rescoreEPSS 95% · 99th percentile
  34. 2026-09-04 05:04 UTCEPSS rescoreEPSS 95% · 99th percentile
  35. 2026-08-30 19:15 UTCEPSS rescoreEPSS 95% · 99th percentile
  36. 2026-08-30 01:20 UTCEPSS rescoreEPSS 95% · 99th percentile
  37. 2026-08-28 21:39 UTCEPSS rescoreEPSS 95% · 99th percentile
  38. 2026-08-16 02:12 UTCEPSS rescoreEPSS 95% · 99th percentile
  39. 2026-08-11 13:40 UTCEPSS rescoreEPSS 95% · 99th percentile
  40. 2026-07-28 15:34 UTCEPSS rescoreEPSS 95% · 99th percentile
  41. 2026-07-23 14:16 UTCEPSS rescoreEPSS 95% · 99th percentile
  42. 2026-07-23 02:30 UTCEG score recompute
  43. 2026-07-22 23:17 UTCEG score recompute
  44. 2026-07-21 15:23 UTCEPSS rescoreEPSS 95% · 99th percentile
  45. 2026-07-20 17:06 UTCEPSS rescoreEPSS 95% · 99th percentile
  46. 2026-07-01 15:05 UTCEPSS rescoreEPSS 95% · 99th percentile
  47. 2026-06-30 23:21 UTCEPSS rescoreEPSS 95% · 99th percentile
  48. 2026-06-29 14:05 UTCEPSS rescoreEPSS 95% · 99th percentile
  49. 2026-06-24 14:04 UTCEPSS rescoreEPSS 95% · 99th percentile
  50. 2026-06-23 21:31 UTCEPSS rescoreEPSS 95% · 99th percentile
  51. 2026-06-16 17:51 UTCEPSS rescoreEPSS 95% · 99th percentile
  52. 2026-06-15 17:47 UTCEPSS rescoreEPSS 95% · 99th percentile
  53. 2026-06-06 13:46 UTCEPSS rescoreEPSS 93% · 99th percentile
  54. 2026-05-31 00:15 UTCEPSS rescoreEPSS 93% · 99th percentile
  55. 2026-05-26 13:43 UTCEPSS rescoreEPSS 93% · 99th percentile
  56. 2026-05-24 09:52 UTCEG score recompute
  57. 2026-05-24 09:52 UTCGHSA enrichmentGHSA-f8xf-39w2-mrc6 · GitHub severity CRITICAL · GitHub CVSS 9.8

Publicly available exploits

(7 references)

Public exploit code is referenced for this CVE (1 Metasploit module, 1 Exploit-DB entry, 3 GitHub PoCs), as are 1 Nuclei detection template, 1 GitHub checker repository. A detection template checks whether a system is affected; it is not necessarily exploit code. A GitHub repository named or described as a checker or scanner checks whether a system is affected; it is not necessarily exploit code. Defenders should treat patch urgency accordingly.

  • Metasploitexploit/multi/http/fortra_goanywhere_mft_rce_cve_2024_0204✓ verified
    Published Feb 2, 2024

    Fortra GoAnywhere MFT Unauthenticated Remote Code Execution

    Open source ↗
  • GitHub PoCibrahmsql/CVE-2024-0204
    Published Jun 15, 2025

    Fortra GoAnywhere MFT 7.4.1 - Authentication Bypass

    Open source ↗
  • Exploit-DBEDB-52308
    Published May 29, 2025

    Fortra GoAnywhere MFT 7.4.1 - Authentication Bypass

    Open source ↗
  • GitHub PoCm-cetin/CVE-2024-0204
    Published Jan 24, 2024

    This script exploits the CVE-2024-0204 vulnerability in Fortra GoAnywhere MFT, allowing the creation of unauthorized administrative users, for educational and authorized testing purposes.

    Open source ↗
  • Nucleihttp/cves/2024/CVE-2024-0204.yaml
    Published Jan 24, 2024

    Fortra GoAnywhere MFT - Authentication Bypass

    Open source ↗
  • GitHub checkercbeek-r7/CVE-2024-0204
    Published Jan 23, 2024

    Scanning for vulnerable GoAnywhere MFT CVE-2024-0204

    Open source ↗
  • GitHub PoChorizon3ai/CVE-2024-0204
    Published Jan 23, 2024

    Authentication Bypass in GoAnywhere MFT

    Open source ↗

Frequently asked(5)

What is CVE-2024-0204?
CVE-2024-0204 is a critical-severity vulnerability; its CVE record was published on January 22, 2024. Authentication bypass in Fortra's GoAnywhere MFT prior to 7.4.1 allows an unauthorized user to create an admin user via the administration portal.
When was the CVE record for CVE-2024-0204 published?
The CVE record for CVE-2024-0204 was published on January 22, 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 21, 2024; the record at its source may have been updated since.
Is CVE-2024-0204 actively exploited?
CVE-2024-0204 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: a Metasploit module exists for it. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 95% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-0204?
CVE-2024-0204 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2024-0204?
The CVE record's solution for CVE-2024-0204, written by its CNA Fortra, LLC, names the fix: "Upgrade to version 7.4.1 or higher."

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2024-0204?

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