How severe is CVE-2024-39330?

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

Is CVE-2024-39330 being actively exploited?

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

What products are affected by CVE-2024-39330?

CVE-2024-39330 affects Djangoproject Django. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2024-39330?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

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

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

When was CVE-2024-39330 published?

CVE-2024-39330 was published on 2024-07-10 and last updated on 2026-06-17.

CVE-2024-39330

CVE-2024-39330 is a medium-severity vulnerability in Djangoproject Django with a CVSS 3.x base score of 4.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-22.

Key facts

Severity: Medium (CVSS 3.x base score 4.3)
EPSS exploit prediction: 1% (62nd percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2024-0042
Weakness: CWE-22
Affected product: Djangoproject Django
Published: 2024-07-10
Last modified: 2026-06-17

Description

An issue was discovered in Django 5.0 before 5.0.7 and 4.2 before 4.2.14. Derived classes of the django.core.files.storage.Storage base class, when they override generate_filename() without replicating the file-path validations from the parent class, potentially allow directory traversal via certain inputs during a save() call. (Built-in Storage sub-classes are unaffected.)

Frequently asked questions

What is CVE-2024-39330?: An issue was discovered in Django 5.0 before 5.0.7 and 4.2 before 4.2.14. Derived classes of the django.core.files.storage.Storage base class, when they override generate_filename() without replicating the file-path validations from the parent class, potentially allow directory traversal via certain inputs during a save() call. (Built-in Storage sub-classes are unaffected.)
How severe is CVE-2024-39330?: CVE-2024-39330 has a CVSS 3.x base score of 4.3, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability none.
Is CVE-2024-39330 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (62nd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2024-39330?: CVE-2024-39330 affects Djangoproject Django. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2024-39330?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2024-39330 have an EU (EUVD) identifier?: Yes. CVE-2024-39330 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-0042.
When was CVE-2024-39330 published?: CVE-2024-39330 was published on 2024-07-10 and last updated on 2026-06-17.

References

Affected products (1)

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

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-22 (Path Traversal) vulnerabilities

CVE-2026-55393 — Critical (CVSS 10.0): Unvalidated pathnames in the web interface in Teledyne FLIR Aware2 versions through 6.9.0.2 (PackBot) and 1.7.9…
CVE-2026-97163 — Critical (CVSS 10.0): Joomla Extension - lomart.fr - Unauthenticated remote code installation in UP plugin extension 5.0.0-5.2.0, 6.0.0-6.0.29
CVE-2026-80155 — Critical (CVSS 10.0): Lantronix SLC8000 before firmware v9.7.0.5, SLC9000 before firmware v9.7.0.2, EMG8500/EMG7500 before firmware v9.7.0.1,…
CVE-2026-70200 — Critical (CVSS 10.0): Improper limitation of a pathname to a restricted directory ('path traversal') in Azure Logic Apps allows an…
CVE-2026-85706 — Critical (CVSS 10.0): GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.7 before 18.11.12, 19.0 before 19.0.9,…
CVE-2026-76606 — Critical (CVSS 10.0): Joomla Extension - fabrikar.com - Path Traversal via image element in Fabrik < 4.7.2.

Browse all CWE-22 (Path Traversal) vulnerabilities →