How severe is CVE-2007-0405?

No CVSS score has been assigned to CVE-2007-0405 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2007-0405?

CVE-2007-0405 affects the following packages: django (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2007-0405?

Update django to 1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2007-0405 is resolved across your whole dependency graph.

How do I detect CVE-2007-0405 in my PyPI dependencies?

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.

How do I mitigate CVE-2007-0405 if there is no patch (or I can't update yet)?

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.

Is CVE-2007-0405 actively exploited in the wild?

No public exploit code has been indexed for CVE-2007-0405 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2007-0405?

CVE-2007-0405 has an EPSS (Exploit Prediction Scoring System) score of 1.3%, placing it in the 71th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was CVE-2007-0405 published, and has it been updated?

CVE-2007-0405 was published on January 23, 2007 and was last updated on July 6, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

CVE-2007-0405 — django

Fix: django/django@3c57822

CVE-2007-0405 is a security vulnerability in django. A fix is available for django — see the affected versions and patch details below.

Django Improper Access Control

Also known asGHSA-mwv2-398h-v489PYSEC-2026-629

Published

Jan 23, 2007

Updated

Jul 6, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs71th percentile — riskier than 71% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐍django

Real-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

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`django`	≥ 0.95&&< 1.0	1.0`pip install --upgrade 'django==1.0'`

Affected Products

1 product · 1 configurations

Application

djangodjango_project

1 version

0.95

Detection & mitigation playbook

Open-source dependency

Detect
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 1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2007-0405 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.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2007-0405 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works