Loading vulnerability…
CVE-2025-13473 is a low-severity information disclosure issue in Django's mod_wsgi authentication path. The vulnerability is in django.contrib.auth.handlers.modwsgi.check_password(), where observable timing differences during authentication can allow a remote attacker to distinguish valid from invalid usernames. Affected versions are Django 6.0 before 6.0.2, 5.2 before 5.2.11, and 4.2 before 4.2.28. The advisory also notes that earlier unsupported series, including 5.0.x, 4.1.x, and 3.2.x, were not evaluated and may also be affected. The issue enables username enumeration through a timing side channel rather than direct authentication bypass.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Low-severity timing side-channel in Django’s mod_wsgi authentication handler enabling remote username enumeration via response-time differences in check_password().
A low-severity timing side-channel in Django’s mod_wsgi authentication handler that can allow remote user enumeration based on response timing differences.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.