Summary
An issue was discovered in 6.0 before 6.0.2, 5.2 before 5.2.11, and 4.2 before 4.2.28.
The django.contrib.auth.handlers.modwsgi.check_password() function for authentication via mod_wsgi allows remote attackers to enumerate users via a timing attack. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.
Django would like to thank Stackered for reporting this issue.
Impact
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Django to 6.0.2 or later; Django to 5.2.11 or later; Django to 4.2.28 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2025-13473? CVE-2025-13473 is a low-severity security vulnerability in Django (pip), affecting versions >= 6.0a1, < 6.0.2. It is fixed in 6.0.2, 5.2.11, 4.2.28.
- Which versions of Django are affected by CVE-2025-13473? Django (pip) versions >= 6.0a1, < 6.0.2 is affected.
- Is there a fix for CVE-2025-13473? Yes. CVE-2025-13473 is fixed in 6.0.2, 5.2.11, 4.2.28. Upgrade to this version or later.
- Is CVE-2025-13473 exploitable, and should I be worried? Whether CVE-2025-13473 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-13473 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-13473?
- Upgrade
Djangoto 6.0.2 or later - Upgrade
Djangoto 5.2.11 or later - Upgrade
Djangoto 4.2.28 or later
- Upgrade