CVE-2007-0405 Django Improper Access Control
Remote authenticated users can gain another user's privileges due to improper caching in Django's AuthenticationMiddleware.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2007-0405?
CVE-2007-0405 is a medium-severity vulnerability in n/a, published on 23 Jan 2007. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
The LazyUser class in the AuthenticationMiddleware for Django 0.95 does not properly cache the user name across requests, which allows remote authenticated users to gain the privileges of a different user.
Which versions are affected by CVE-2007-0405?
3 open source packages ship an affected version, including django and Django. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
django PyPI | From 0.95 | 1.0 |
django PyPI | From 0.95 | 1.0 |
Django PyPI | From 0.95 | 1.0 |
Products include Django Project Django.
How do I fix CVE-2007-0405?
Upgrade django to 1.0 or later.
Is CVE-2007-0405 being exploited?
There is no known exploitation of CVE-2007-0405 in the wild and no public exploit code.
Other vulnerabilities in n/a
- CVE-2007-0404 Django Arbitrary Code Execution
- CVE-2007-5828 Cross-site request forgery in n/a
- CVE-2009-2659 Django Admin Media Handler Vulnerable to Directory Traversal
- CVE-2008-2302 Django Cross-site scripting (XSS) vulnerability
- CVE-2007-5712 Django vulnerable to Denial of Service via i18n middleware component
Sources
Also known as DEBIAN-CVE-2007-0405, GHSA-mwv2-398h-v489, PYSEC-2026-629.