{"answers":{"affected":"3 open source packages ship an affected version, including django and Django. It affects 1 product.","exploited":"There is no known exploitation of CVE-2007-0405 in the wild and no public exploit code.","fix":"Upgrade django to 1.0 or later.","what":"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."},"fix_prompt":"Check this codebase for CVE-2007-0405 and fix it if it is affected.\n\nWhat it is: 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.\nExploitation: There is no known exploitation of CVE-2007-0405 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- django (PyPI): affected from 0.95; fixed in 1.0\n- django (PyPI): affected from 0.95; fixed in 1.0\n- Django (PyPI): affected from 0.95; fixed in 1.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2007-0405/ (Markdown: https://insights.sbomify.com/CVE-2007-0405/index.md)","id":"CVE-2007-0405","markdown":"https://insights.sbomify.com/CVE-2007-0405/index.md","name":"CVE-2007-0405","record":{"aliases":["DEBIAN-CVE-2007-0405","GHSA-mwv2-398h-v489","PYSEC-2026-629"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Django web framework","requires_auth":"low_privilege","summary":"Remote authenticated users can gain another user's privileges due to improper caching in Django's AuthenticationMiddleware.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"django","vendor":"django_project"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:S/C:P/I:P/A:P","version":"2.0"},"cwes":[],"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Django Improper Access Control","id":"CVE-2007-0405","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"privilege_escalation","year":"2007"},"n_packages":3,"n_references":4,"next":{"headline":"Memory corruption in n/a","id":"CVE-2007-0406"},"packages":[{"ecosystem":"PyPI","fixed":["1.0"],"introduced":["0.95"],"last_affected":[],"package":"Django","purl":null,"source":"GHSA-mwv2-398h-v489"},{"ecosystem":"PyPI","fixed":["1.0"],"introduced":["0.95"],"last_affected":[],"package":"django","purl":"pkg:pypi/django","source":"GHSA-mwv2-398h-v489"},{"ecosystem":"PyPI","fixed":["1.0"],"introduced":["0.95"],"last_affected":[],"package":"django","purl":"pkg:pypi/django","source":"PYSEC-2026-629"}],"prev":{"headline":"Django Arbitrary Code Execution","id":"CVE-2007-0404"},"products":["n/a"],"published":"2007-01-23","related":[{"cvss_score":7.5,"headline":"Django Arbitrary Code Execution","id":"CVE-2007-0404","kev_date_added":null,"published":"2007-01-23"},{"cvss_score":6.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2007-5828","kev_date_added":null,"published":"2007-11-05"},{"cvss_score":5,"headline":"Django Admin Media Handler Vulnerable to Directory Traversal","id":"CVE-2009-2659","kev_date_added":null,"published":"2009-08-04"},{"cvss_score":4.3,"headline":"Django Cross-site scripting (XSS) vulnerability","id":"CVE-2008-2302","kev_date_added":null,"published":"2008-05-23"},{"cvss_score":2.6,"headline":"Django vulnerable to Denial of Service via i18n middleware component","id":"CVE-2007-5712","kev_date_added":null,"published":"2007-10-30"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Remote authenticated users can gain another user's privileges due to improper caching in Django's AuthenticationMiddleware.","url":"https://insights.sbomify.com/CVE-2007-0405/"}