ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2024-39329

CVE-2024-39329 is listed by An issue was discovered in Django 5.0 before 5.0.7 and 4.2 before 4.2.14..

Published Jul 10, 2024 · catalog updated Jun 17, 2026 · the affected product

Last checked Nov 8, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2024-39329. EPSS is 0.89%. Act only if a listed version of the affected product is installed.

Gaps on this record

  • No plain product name is stored. The page cannot tell you which product to check.
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.

Same product and reporting

Severity
Medium5.3
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.89%
Remediation
Version ranges on file
Affected products
cpe djangoproject/django

CVE-2024-39329 is listed by An issue was discovered in Django 5.0 before 5.0.7 and 4.2 before 4.2.14..

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe djangoproject/django< 4.2.14
  • cpe djangoproject/django< 5.0.7

How to fix CVE-2024-39329

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2024-39329. EPSS is 0.89%. Act only if a listed version of the affected product is installed.

Which versions are affected?

Compare what you have installed with < 4.2.14, < 5.0.7. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-208. EPSS 0.89%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Django security

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Jul 10, 2024 · Monitored products — high

    Detected

    CVE-2024-39329 is listed by An issue was discovered in Django 5.0 before 5.0.7 and 4.2 before 4.2.14..

  2. Jun 17, 2026 · Monitored products — high

    Updated

    CVE-2024-39329 is listed by An issue was discovered in Django 5.0 before 5.0.7 and 4.2 before 4.2.14..

Sources

  • CVE.orgVulnerability recordCVE-2024-39329

    Official CVE identifier

    cve.org
  • Monitored products — highVendor advisoryCVE-2024-39329

    An issue was discovered in Django 5.0 before 5.0.7 and 4.2 before 4.2.14. The django.contrib.auth.backends.ModelBackend.authenticate() method allows remote attackers to enumerate users via a timing attack involving login requests for users with an unusable password.

    nvd.nist.gov

References

Freshness

Last verified in this catalog Nov 7, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • CVE.orgNov 8, 2026
  • Monitored products — highNov 7, 2026