CVE-2007-0405: PYSEC-2026-629 - Django Improper Access Control

CVE-2007-0405 · Severity: info · Published 2026-07-02

Django Improper Access Control

Technologies: Django (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2007-0405 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2007-0405 being exploited in the wild.
How severe is CVE-2007-0405?
Informational severity, published 2 July 2026.
Which products and versions are affected?
Django (PyPI) ECOSYSTEM:introduced=0.95,fixed=1.0.
Is there a fix for CVE-2007-0405?
Yes. Django (PyPI): upgrade to 1.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2007-0405?
Check whether you run Django (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • Django (PyPI): upgrade to 1.0 or later
    pip install "Django>=1.0"

Affected products

  • Django (PyPI) ECOSYSTEM:introduced=0.95,fixed=1.0

Identifiers

  • CVE-2007-0405
  • GHSA-mwv2-398h-v489
  • PYSEC-2026-629

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.