CVE-2025-13473 — django
MEDIUMCVE-2025-13473 is a medium-severity (CVSS 5.3) CWE-208 vulnerability in django. A fix is available for django — see the affected versions and patch details below.
Username enumeration through timing difference in mod_wsgi authentication handler
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-13473.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
django🐍django🐍djangoReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | django | ≥ 6.0a1&&< 6.0.2 | 6.0.2pip install --upgrade 'django==6.0.2' |
| 🐍PyPI | django | ≥ 5.2a1&&< 5.2.11 | 5.2.11pip install --upgrade 'django==5.2.11' |
| 🐍PyPI | django | ≥ 4.2a1&&< 4.2.28 | 4.2.28pip install --upgrade 'django==4.2.28' |
Affected Products
djangodjangoprojectDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for django, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update django to 6.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-13473 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
This LOW impact vulnerability in Django allows for user enumeration via a timing attack when `mod_wsgi` authentication is utilized. An attacker could exploit timing differences in the `check_password()` function to determine valid usernames on affected Red Hat products that use Django with `mod_wsgi` for…
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.Source: Red Hat security advisory for CVE-2025-13473 (CC BY 4.0)
Frequently Asked Questions
Is CVE-2025-13473 in your dependencies?
Find it across PyPI, including transitive dependencies.