CVE-2024-55924

HIGHNVD 8.08.0
EchelonGraph scoreMEDIUM confidence

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

Score 8.0 from GitHub Security Advisory (severity: HIGH) published 2025-01-14. NVD baseline CVSS 8.0; 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-2025-0062 (ENISA EUVD) · GHSA-7835-fcv3-g256 (GitHub Security Advisories)Source: ENISA EUVD

8.0EG
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.3%CVSS: 8.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

TYPO3 is a free and open source Content Management Framework. A vulnerability has been identified in the backend user interface functionality involving deep links. Specifically, this functionality is susceptible to Cross-Site Request Forgery (CSRF). Additionally, state-changing actions in downstream components incorrectly accepted submissions via HTTP GET and did not enforce the appropriate HTTP method. Successful exploitation of this vulnerability requires the victim to have an active session on the backend user interface and to be deceived into interacting with a malicious URL targeting the backend, which can occur under the following conditions: The user opens a malicious link, such as one sent via email. The user visits a compromised or manipulated website while the following settings are misconfigured: 1. security.backend.enforceReferrer feature is disabled, 2. BE/cookieSameSite configuration is set to lax or none. The vulnerability in the affected downstream component “Scheduler Module” allows attackers to trigger pre-defined command classes - which can lead to unauthorized import or export of data in the worst case. Users are advised to update to TYPO3 versions 11.5.42 ELTS which fixes the problem described. There are no known workarounds for this vulnerability.

CVSS v3
8.0
EG Score
8.0HIGHmedium confidence
EG Risk
36
EG Risk 36/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)
Severity80% × 45%
Impact severity (EG Severity): CVSS 8.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 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.3%
EPSS %ILE
18th
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.0): severity, escalated by confirmed exploitation. This CVE's 8.0 is its impact severity (EG Severity), not escalated.

EG Severity
8.0 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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 14, 2025

Last Modified

August 26, 2025

Advisory Details (2)

Auto-updated Sep 20, 2026
Patch available. Sources: github.
Web page

TYPO3-CORE-SA-2025-009: Cross-Site Request Forgery in Scheduler Module - TYPO3 News

https://typo3.org/security/advisory/typo3-core-sa-2025-009
GitHub advisoryMentions a patch (unverified)

Cross-Site Request Forgery in Scheduler Module · Advisory · TYPO3/typo3 · GitHub

https://github.com/TYPO3/typo3/security/advisories/GHSA-7835-fcv3-g256

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
composertypo3/cms-scheduler @ 11.5.42 (fixes >= 11.0.0, <= 11.5.41)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFix by version rangeDependents
typo3/cms-schedulerv11.0.0 ... v11.5.9 (51 versions)
  • 11.0.0 up to 11.5.42: fixed in 11.5.42
—

Weakness Classification(2)

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

Data Freshness Timeline

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

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2024-55924?
CVE-2024-55924 is a high-severity vulnerability; its CVE record was published on January 14, 2025. TYPO3 is a free and open source Content Management Framework. A vulnerability has been identified in the backend user interface functionality involving deep links. Specifically, this functionality is susceptible to Cross-Site Request Forgery (CSRF). Additionally, state-changing actions in…
When was the CVE record for CVE-2024-55924 published?
The CVE record for CVE-2024-55924 was published on January 14, 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 26, 2025; the record at its source may have been updated since.
Is CVE-2024-55924 actively exploited?
CVE-2024-55924 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (18th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-55924?
CVE-2024-55924 has a CVSS v3 base score of 8.0 (NVD).
How do I remediate CVE-2024-55924?
A fix for CVE-2024-55924 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-55924

Explore →

Is Your Infrastructure Affected by CVE-2024-55924?

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

Book a Demo →Browse All CVEs