{"answers":{"affected":"5 open source packages ship an affected version, including django and Django. It affects 1 product.","exploited":"There is no known exploitation of CVE-2011-0696 in the wild and no public exploit code.","fix":"Upgrade django to a fixed version for your release line: 1.1.4 or 1.2.5.","what":"CVE-2011-0696 is a medium-severity vulnerability in Djangoproject Django, published on 14 Feb 2011. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2011-0696 and fix it if it is affected.\n\nWhat it is: CVE-2011-0696 is a medium-severity vulnerability in Djangoproject Django, published on 14 Feb 2011. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2011-0696 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- django (PyPI): affected from 1.1; fixed in 1.1.4, 1.2.5\n- django (PyPI): affected from 1.1; fixed in 1.1.4\n- django (PyPI): affected from 1.2; fixed in 1.2.5\n- Django (PyPI): affected from 1.1; fixed in 1.1.4\n- Django (PyPI): affected from 1.2; fixed in 1.2.5\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-2011-0696/ (Markdown: https://insights.sbomify.com/CVE-2011-0696/index.md)","id":"CVE-2011-0696","markdown":"https://insights.sbomify.com/CVE-2011-0696/index.md","name":"CVE-2011-0696","record":{"aliases":["DEBIAN-CVE-2011-0696","GHSA-5j2h-h5hg-3wf8","PYSEC-2011-10"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Django web framework","requires_auth":"none","summary":"Remote attackers can bypass CSRF protections in Django applications by forging AJAX requests, potentially allowing unauthorized actions on behalf of authenticated users.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"django","vendor":"djangoproject"}],"cvss":{"score":6.8,"severity":"medium","source":"nvd","vector":"AV:N/AC:M/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Django 1.1.x before 1.1.4 and 1.2.x before 1.2.5 does not properly validate HTTP requests that contain an X-Requested-With header, which makes it easier for remote attackers to conduct cross-site request forgery (CSRF) attacks via forged AJAX requests that leverage a \"combination of browser plugins and redirects,\" a related issue to CVE-2011-0447.","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":"Cross-site request forgery in Django","id":"CVE-2011-0696","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":"djangoproject:django","products":["djangoproject:django"],"type":"csrf","year":"2011"},"n_packages":5,"n_references":18,"next":{"headline":"Cross-site scripting in django","id":"CVE-2011-0697"},"packages":[{"ecosystem":"PyPI","fixed":["1.1.4"],"introduced":["1.1"],"last_affected":[],"package":"Django","purl":null,"source":"GHSA-5j2h-h5hg-3wf8"},{"ecosystem":"PyPI","fixed":["1.2.5"],"introduced":["1.2"],"last_affected":[],"package":"Django","purl":null,"source":"GHSA-5j2h-h5hg-3wf8"},{"ecosystem":"PyPI","fixed":["1.1.4","1.2.5"],"introduced":["1.1","1.2"],"last_affected":[],"package":"django","purl":"pkg:pypi/django","source":"PYSEC-2011-10"},{"ecosystem":"PyPI","fixed":["1.1.4"],"introduced":["1.1"],"last_affected":[],"package":"django","purl":"pkg:pypi/django","source":"GHSA-5j2h-h5hg-3wf8"},{"ecosystem":"PyPI","fixed":["1.2.5"],"introduced":["1.2"],"last_affected":[],"package":"django","purl":"pkg:pypi/django","source":"GHSA-5j2h-h5hg-3wf8"}],"prev":{"headline":"Race condition in n/a","id":"CVE-2011-0695"},"products":["n/a"],"published":"2011-02-14","related":[{"cvss_score":9.8,"headline":"Privilege abuse in GenericInlineModelAdmin","id":"CVE-2026-4277","kev_date_added":null,"published":"2026-04-07"},{"cvss_score":9.8,"headline":"Django SQL injection in HasKey(lhs, rhs) on Oracle","id":"CVE-2024-53908","kev_date_added":null,"published":"2024-12-06"},{"cvss_score":9.8,"headline":"Django SQL injection vulnerability","id":"CVE-2024-42005","kev_date_added":null,"published":"2024-08-07"},{"cvss_score":9.8,"headline":"Django bypasses validation when using one form field to upload multiple files","id":"CVE-2023-31047","kev_date_added":null,"published":"2023-05-07"},{"cvss_score":9.8,"headline":"Django `Trunc()` and `Extract()` database functions vulnerable to SQL Injection","id":"CVE-2022-34265","kev_date_added":null,"published":"2022-07-04"},{"cvss_score":9.8,"headline":"SQL Injection in Django","id":"CVE-2021-35042","kev_date_added":null,"published":"2021-07-02"},{"cvss_score":9.8,"headline":"SQL injection in Django","id":"CVE-2020-7471","kev_date_added":null,"published":"2020-02-03"}],"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["n/a"]},"summary":"Remote attackers can bypass CSRF protections in Django applications by forging AJAX requests, potentially allowing unauthorized actions on behalf of authenticated users.","url":"https://insights.sbomify.com/CVE-2011-0696/"}