CVE-2024-56320

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.7% (54th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3

Also known asEUVD-2024-53109 (ENISA EUVD)Source: ENISA EUVD

8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

GoCD is a continuous deliver server. GoCD versions prior to 24.5.0 are vulnerable to admin privilege escalation due to improper authorization of access to the admin "Configuration XML" UI feature, and its associated API. A malicious insider/existing authenticated GoCD user with an existing GoCD user account could abuse this vulnerability to access information intended only for GoCD admins, or to escalate their privileges to that of a GoCD admin in a persistent manner. it is not possible for this vulnerability to be abused prior to authentication/login. The issue is fixed in GoCD 24.5.0. GoCD users who are not able to immediate upgrade can mitigate this issue by using a reverse proxy, WAF or similar to externally block access paths with a /go/rails/ prefix. Blocking this route causes no loss of functionality. If it is not possible to upgrade or block the above route, consider reducing the GoCD user base to more trusted set of users, including temporarily disabling use of plugins such as the guest-login-plugin, which allow limited anonymous access as a regular user account.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/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)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (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: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.7%
EPSS %ILE
54th
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 (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-02). 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; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade 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; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (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 3, 2025

Last Modified

August 1, 2025

Advisory Details (4)

Auto-updated Aug 13, 2026
Patch available. Sources: github_commit, github_release, github.
Web page

Releases - Version notes | GoCD

https://www.gocd.org/releases/#24-5-0
GitHub advisoryMentions a patch (unverified)

GoCD before 24.5.0 is vulnerable to admin privilege escalation by a malicious internal & authenticated user · Advisory · gocd/gocd · GitHub

https://github.com/gocd/gocd/security/advisories/GHSA-346h-q594-rj8j
GitHub release Patch Available

GoCD 24.5.0

Patch available: gocd/gocd 24.5.0

https://github.com/gocd/gocd/releases/tag/24.5.0
GitHub commit Patch Available

commit 68b598b97bd2 (gocd/gocd)

Patch available: gocd/gocd 24.5.0 (contains commit 68b598b97bd2)

https://github.com/gocd/gocd/commit/68b598b97bd283a5a85e20d018d69fe86acf4165

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 36× 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 95 of 196 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. 5 repeat rows among the latest 100 are merged into the row they repeat. The 101 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2024-56320?
CVE-2024-56320 is a high-severity vulnerability; its CVE record was published on January 3, 2025. GoCD is a continuous deliver server. GoCD versions prior to 24.5.0 are vulnerable to admin privilege escalation due to improper authorization of access to the admin "Configuration XML" UI feature, and its associated API. A malicious insider/existing authenticated GoCD user with an existing GoCD…
When was the CVE record for CVE-2024-56320 published?
The CVE record for CVE-2024-56320 was published on January 3, 2025. 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 August 1, 2025; the record at its source may have been updated since.
Is CVE-2024-56320 actively exploited?
CVE-2024-56320 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (54th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-56320?
CVE-2024-56320 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2024-56320?
A fix for CVE-2024-56320 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-56320

Explore →

Is Your Infrastructure Affected by CVE-2024-56320?

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

Book a Demo →Browse All CVEs