How severe is CVE-2024-45230?

CVE-2024-45230 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.

Is CVE-2024-45230 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 25% (98th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2024-45230?

CVE-2024-45230 primarily affects Djangoproject Django. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2024-45230?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2024-45230 have an EU (EUVD) identifier?

Yes. CVE-2024-45230 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-0037.

When was CVE-2024-45230 published?

CVE-2024-45230 was published on 2024-10-08 and last updated on 2026-06-17.

CVE-2024-45230

CVE-2024-45230 is a high-severity vulnerability in Djangoproject Django with a CVSS 3.x base score of 7.5. Its EPSS exploit-prediction score of 25% places it in the 98th percentile, indicating an elevated likelihood of exploitation. The underlying weakness is classified as CWE-120.

Key facts

Severity: High (CVSS 3.x base score 7.5)
EPSS exploit prediction: 25% (98th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2024-0037
Weakness: CWE-120
Affected product: Djangoproject Django
Published: 2024-10-08
Last modified: 2026-06-17

Description

An issue was discovered in Django 5.1 before 5.1.1, 5.0 before 5.0.9, and 4.2 before 4.2.16. The urlize() and urlizetrunc() template filters are subject to a potential denial-of-service attack via very large inputs with a specific sequence of characters.

Frequently asked questions

What is CVE-2024-45230?: An issue was discovered in Django 5.1 before 5.1.1, 5.0 before 5.0.9, and 4.2 before 4.2.16. The urlize() and urlizetrunc() template filters are subject to a potential denial-of-service attack via very large inputs with a specific sequence of characters.
How severe is CVE-2024-45230?: CVE-2024-45230 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
Is CVE-2024-45230 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 25% (98th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2024-45230?: CVE-2024-45230 primarily affects Djangoproject Django. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2024-45230?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2024-45230 have an EU (EUVD) identifier?: Yes. CVE-2024-45230 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-0037.
When was CVE-2024-45230 published?: CVE-2024-45230 was published on 2024-10-08 and last updated on 2026-06-17.

References

Affected products (2)

cpe:2.3:a:djangoproject:django:*:*:*:*:*:*:*:*
cpe:2.3:a:djangoproject:django:5.1:*:*:*:*:*:*:*

More vulnerabilities in Djangoproject Django

CVE-2014-0474 — Critical (CVSS 10.0): The (1) FilePathField, (2) GenericIPAddressField, and (3) IPAddressField model field classes in Django before 1.4.11,…
CVE-2026-4277 — Critical (CVSS 9.8): An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. Add permissions on inline model…
CVE-2024-53908 — Critical (CVSS 9.8): An issue was discovered in Django 5.1 before 5.1.4, 5.0 before 5.0.10, and 4.2 before 4.2.17. Direct usage of the…
CVE-2023-31047 — Critical (CVSS 9.8): In Django 3.2 before 3.2.19, 4.x before 4.1.9, and 4.2 before 4.2.1, it was possible to bypass validation when using…
CVE-2022-34265 — Critical (CVSS 9.8): An issue was discovered in Django 3.2 before 3.2.14 and 4.0 before 4.0.6. The Trunc() and Extract() database functions…
CVE-2022-28347 — Critical (CVSS 9.8): A SQL injection issue was discovered in QuerySet.explain() in Django 2.2 before 2.2.28, 3.2 before 3.2.13, and 4.0…

All CVEs affecting Djangoproject Django →

Other CWE-120 (Classic Buffer Overflow) vulnerabilities

CVE-2025-48611 — Critical (CVSS 10.0): In DeviceId of DeviceId.java, there is a possible desync in persistence due to a missing bounds check. This could lead…
CVE-2026-24823 — Critical (CVSS 10.0): Out-of-bounds Write, Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') vulnerability in FASTSHIFT…
CVE-2026-24810 — Critical (CVSS 10.0): Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') vulnerability in rethinkdb (src/cjson modules).…
CVE-2026-24800 — Critical (CVSS 10.0): Out-of-bounds Write, Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') vulnerability in tildearrow…
CVE-2025-9962 — Critical (CVSS 10.0): A buffer overflow vulnerability in Novakon P series allows attackers to gain root permission without prior…
CVE-2010-10016 — Critical (CVSS 10.0): BS.Player version 2.57 (build 1051) contains a vulnerability in its playlist import functionality. When processing .m3u…

Browse all CWE-120 (Classic Buffer Overflow) vulnerabilities →