CVE-2024-24680

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 1.6% (76th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 5.9 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2024-02-07) is not newer than that change (2025-11-04), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2024-0038 (ENISA EUVD) · GHSA-xxj9-f6rv-m3x4 (GitHub Security Advisories) · PYSEC-2024-28 (OSV.dev)Source: ENISA EUVD

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

A fix is available — apply it.

An issue was discovered in Django 3.2 before 3.2.24, 4.2 before 4.2.10, and Django 5.0 before 5.0.2. The intcomma template filter was subject to a potential denial-of-service attack when used with very long strings.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/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)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation1.6% × 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 partial (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
1.6%
EPSS %ILE
76th
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 (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 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
1.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-08). 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: 14 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).

A fix is available. 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 partial (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; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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

February 6, 2024

Last Modified

November 4, 2025

Advisory Details (6)

Auto-updated Nov 1, 2026
Patch available.
Web page

[SECURITY] Fedora 39 Update: python-django-4.2.11-2.fc39 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/SN2PLJGYSAAG5KUVIUFJYKD3BLQ4OSN6/
Web page

[SECURITY] Fedora 40 Update: python-django-4.2.11-2.fc40 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/D2JIRXEDP4ZET5KFMAPPYSK663Q52NEX/
Web page

Archive of security issues | Django documentation | Django

https://docs.djangoproject.com/en/5.0/releases/security/
Web page

Django security releases issued: 5.0.2, 4.2.10, and 3.2.24 | Weblog | Django

https://www.djangoproject.com/weblog/2024/feb/06/security-releases/
Web page

[SECURITY] Fedora 38 Update: python-django3-3.2.25-2.fc38 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/ZQJOMNRMVPCN5WMIZ7YSX5LQ7IR2NY4D/

Patch Availability(9)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntupython3-django (2:2.2.12-1ubuntu0.21) @ focal2026-10-27ubuntu
redhatpython-django-0:4.2.14-1.el8pc2024-08-20redhat
redhatpython-django-0:2.2.24-8.el9ost2024-05-22redhat
redhatpython-django-0:4.2.11-1.el8ui2024-04-18redhat
redhatautomation-controller-0:4.5.5-2.el9ap2024-04-02redhat
redhatpython-django-0:4.2.10-1.el9ap2024-02-29redhat
pipdjango @ 4.2.10 (fixes >= 4.2, < 4.2.10)—ghsa
pipdjango @ 5.0.2 (fixes >= 5.0, < 5.0.2)—ghsa
pipDjango @ 3.2.24 (fixes >= 3.2, < 3.2.24)—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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
python-django2:2.2.24-1 ... 2:2.2.28-1~deb11u6 (9 versions)
  • every version up to 2:2.2.28-1~deb11u7: fixed in 2:2.2.28-1~deb11u7
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
python-django3:3.2.19-1 ... 3:3.2.21-1 (7 versions)
  • every version up to 3:3.2.25-0+deb12u1: fixed in 3:3.2.25-0+deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
python-django—
  • every version up to 3:4.2.10-1: fixed in 3:4.2.10-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
python-django—
  • every version up to 3:4.2.10-1: fixed in 3:4.2.10-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
django3.2 ... 5.0.1 (36 versions)
  • 3.2 up to 3.2.24: fixed in 3.2.24
  • 4.2 up to 4.2.10: fixed in 4.2.10
  • 5.0 up to 5.0.2: fixed in 5.0.2
—

Weakness Classification(1)

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

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 227 rows on record for this CVE, as 98 entries (2 repeats merged).

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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 127 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-12 16:31 UTCEPSS rescoreEPSS 1.6% · 76th percentile
  2. 2026-11-11 16:34 UTCEPSS rescoreEPSS 1.6% · 76th percentile
  3. 2026-11-10 16:38 UTCEPSS rescoreEPSS 1.6% · 76th percentile
  4. 2026-11-09 16:31 UTCEPSS rescoreEPSS 1.6% · 76th percentile
  5. 2026-11-09 11:58 UTCEchelonGraph re-scored
  6. 2026-11-09 11:58 UTCVendor advisory
  7. 2026-11-09 11:58 UTCGHSA enrichmentGHSA-xxj9-f6rv-m3x4 · GitHub severity HIGH · GitHub CVSS 5.9
  8. 2026-11-08 16:35 UTCEPSS rescoreEPSS 1.6% · 76th percentile
  9. 2026-11-07 16:35 UTCEPSS rescoreEPSS 1.6% · 76th percentile
  10. 2026-11-06 16:31 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  11. 2026-11-05 16:33 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  12. 2026-11-04 16:32 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  13. 2026-11-03 16:42 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  14. 2026-11-03 03:46 UTCEchelonGraph re-scored
  15. 2026-11-03 03:46 UTCVendor advisory
  16. 2026-11-03 03:45 UTCGHSA enrichmentGHSA-xxj9-f6rv-m3x4 · GitHub severity HIGH · GitHub CVSS 5.9
  17. 2026-11-02 16:40 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  18. 2026-11-01 08:15 UTCEchelonGraph re-scored
  19. 2026-11-01 08:15 UTCGHSA enrichmentGHSA-xxj9-f6rv-m3x4 · GitHub severity HIGH · GitHub CVSS 5.9
  20. 2026-10-31 16:30 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  21. 2026-10-30 16:31 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  22. 2026-10-29 16:30 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  23. 2026-10-28 16:29 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  24. 2026-10-27 19:32 UTCEchelonGraph re-scored
  25. 2026-10-27 19:32 UTCVendor advisory
Show 73 more
  1. 2026-10-27 16:29 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  2. 2026-10-26 16:29 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  3. 2026-10-25 17:17 UTCEchelonGraph re-scored
  4. 2026-10-25 16:30 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  5. 2026-10-24 16:30 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  6. 2026-10-23 16:29 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  7. 2026-10-22 16:31 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  8. 2026-10-21 16:29 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  9. 2026-10-20 20:27 UTCEchelonGraph re-scored
  10. 2026-10-20 20:27 UTCVendor advisory
  11. 2026-10-20 16:30 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  12. 2026-10-19 16:29 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  13. 2026-10-18 16:29 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  14. 2026-10-18 07:25 UTCEchelonGraph re-scored
  15. 2026-10-17 16:30 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  16. 2026-10-16 16:36 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  17. 2026-10-15 16:29 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  18. 2026-10-14 16:30 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  19. 2026-10-13 16:30 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  20. 2026-10-12 18:01 UTCEchelonGraph re-scored
  21. 2026-10-12 16:31 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  22. 2026-10-12 02:54 UTCOSV refresh
  23. 2026-10-11 21:25 UTCEchelonGraph re-scored
  24. 2026-10-11 16:19 UTCEchelonGraph re-scored
  25. 2026-10-11 13:45 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  26. 2026-10-10 19:58 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  27. 2026-10-09 20:05 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  28. 2026-10-08 17:07 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  29. 2026-10-07 23:46 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  30. 2026-10-06 15:15 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  31. 2026-10-05 17:41 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  32. 2026-10-03 14:23 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  33. 2026-10-01 19:48 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  34. 2026-09-30 16:58 UTCEchelonGraph re-scored
  35. 2026-09-30 15:01 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  36. 2026-09-29 15:17 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  37. 2026-09-28 13:49 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  38. 2026-09-24 14:01 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  39. 2026-09-23 13:46 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  40. 2026-09-22 09:15 UTCOSV refresh
  41. 2026-09-16 14:06 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  42. 2026-09-16 05:11 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  43. 2026-09-15 03:08 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  44. 2026-09-13 16:45 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  45. 2026-09-12 14:59 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  46. 2026-09-11 14:51 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  47. 2026-09-11 09:34 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  48. 2026-09-08 21:58 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  49. 2026-09-07 15:59 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  50. 2026-09-06 13:46 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  51. 2026-09-05 15:26 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  52. 2026-09-04 13:58 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  53. 2026-09-04 05:05 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  54. 2026-09-03 06:00 UTCOSV refresh
  55. 2026-09-02 14:10 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  56. 2026-09-01 13:52 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  57. 2026-08-30 19:15 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  58. 2026-08-30 01:20 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  59. 2026-08-28 21:39 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  60. 2026-08-27 14:23 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  61. 2026-08-26 14:44 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  62. 2026-08-25 13:47 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  63. 2026-08-23 00:17 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  64. 2026-08-21 23:47 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  65. 2026-08-20 22:53 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  66. 2026-08-19 17:02 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  67. 2026-08-18 13:46 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  68. 2026-08-17 13:45 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  69. 2026-08-16 19:26 UTCOSV refresh
  70. 2026-08-16 14:54 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  71. 2026-08-16 02:12 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  72. 2026-08-15 01:28 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  73. 2026-08-13 21:58 UTCEPSS rescoreEPSS 1.6% · 73rd percentile

Frequently asked(5)

What is CVE-2024-24680?
CVE-2024-24680 is a high-severity vulnerability; its CVE record was published on February 6, 2024. An issue was discovered in Django 3.2 before 3.2.24, 4.2 before 4.2.10, and Django 5.0 before 5.0.2. The intcomma template filter was subject to a potential denial-of-service attack when used with very long strings.
When was the CVE record for CVE-2024-24680 published?
The CVE record for CVE-2024-24680 was published on February 6, 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 4, 2025; the record at its source may have been updated since.
Is CVE-2024-24680 actively exploited?
CVE-2024-24680 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.6% probability of exploitation in the next 30 days (76th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-24680?
CVE-2024-24680 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2024-24680?
A fix for CVE-2024-24680 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-24680 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2024-24680?

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