{"answers":{"affected":"7 open source packages ship an affected version, including django and Django. It affects 1 product.","exploited":"There is no known exploitation of CVE-2015-8213 in the wild and no public exploit code.","fix":"Upgrade django to a fixed version for your release line: 1.7.11, 1.8.7 or 1.9rc2.","what":"CVE-2015-8213 is a medium-severity vulnerability in Djangoproject Django, published on 7 Dec 2015. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2015-8213 and fix it if it is affected.\n\nWhat it is: CVE-2015-8213 is a medium-severity vulnerability in Djangoproject Django, published on 7 Dec 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2015-8213 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- django (PyPI): affected all versions; fixed in 1.7.11, 1.8.7, 1.9rc2\n- django (PyPI): affected from 1.7; fixed in 1.7.11\n- django (PyPI): affected from 1.8a1; fixed in 1.8.7\n- django (PyPI): affected from 1.9a1; fixed in 1.9rc2\n- Django (PyPI): affected from 1.7; fixed in 1.7.11\n- Django (PyPI): affected from 1.8a1; fixed in 1.8.7\n- Django (PyPI): affected from 1.9a1; fixed in 1.9rc2\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-2015-8213/ (Markdown: https://insights.sbomify.com/CVE-2015-8213/index.md)","id":"CVE-2015-8213","markdown":"https://insights.sbomify.com/CVE-2015-8213/index.md","name":"CVE-2015-8213","record":{"aliases":["DEBIAN-CVE-2015-8213","DLA-349-1","DSA-3404-1","GHSA-6wcr-wcqm-3mfh","MGASA-2015-0463","PYSEC-2015-11","RHSA-2016:0129","RHSA-2016:0156","RHSA-2016:0157","RHSA-2016:0158","RHSA-2016:0360","SUSE-SU-2015:2327-1","SUSE-SU-2016:0040-1","UBUNTU-CVE-2015-8213","USN-2816-1"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Django web framework","requires_auth":"none","summary":"Remote attackers can obtain sensitive application secrets like SECRET_KEY by manipulating date/time format settings in Django.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"django","vendor":"djangoproject"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:N/A:N","version":"2.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"The get_format function in utils/formats.py in Django before 1.7.x before 1.7.11, 1.8.x before 1.8.7, and 1.9.x before 1.9rc2 might allow remote attackers to obtain sensitive application secrets via a settings key in place of a date/time format setting, as demonstrated by SECRET_KEY.","ecosystems":["PyPI","Red Hat:openstack-optools:7::el7","Red Hat:openstack:5::el6","Red Hat:openstack:5::el7","Red Hat:openstack:6::el7","Red Hat:openstack:7::el7","SUSE:Enterprise Storage 1.0","SUSE:OpenStack Cloud 5"],"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 settings leak in date template filter","id":"CVE-2015-8213","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":"djangoproject:django","products":["djangoproject:django"],"type":"information_disclosure","year":"2015"},"n_packages":23,"n_references":14,"next":{"headline":"Missing authorization in n/a","id":"CVE-2015-8214"},"packages":[{"ecosystem":"PyPI","fixed":["1.7.11"],"introduced":["1.7"],"last_affected":[],"package":"Django","purl":null,"source":"GHSA-6wcr-wcqm-3mfh"},{"ecosystem":"PyPI","fixed":["1.8.7"],"introduced":["1.8a1"],"last_affected":[],"package":"Django","purl":null,"source":"GHSA-6wcr-wcqm-3mfh"},{"ecosystem":"PyPI","fixed":["1.9rc2"],"introduced":["1.9a1"],"last_affected":[],"package":"Django","purl":null,"source":"GHSA-6wcr-wcqm-3mfh"},{"ecosystem":"PyPI","fixed":["1.7.11","1.8.7","1.9rc2"],"introduced":["0","1.8","1.9a0"],"last_affected":[],"package":"django","purl":"pkg:pypi/django","source":"PYSEC-2015-11"},{"ecosystem":"PyPI","fixed":["1.7.11"],"introduced":["1.7"],"last_affected":[],"package":"django","purl":"pkg:pypi/django","source":"GHSA-6wcr-wcqm-3mfh"},{"ecosystem":"PyPI","fixed":["1.8.7"],"introduced":["1.8a1"],"last_affected":[],"package":"django","purl":"pkg:pypi/django","source":"GHSA-6wcr-wcqm-3mfh"},{"ecosystem":"PyPI","fixed":["1.9rc2"],"introduced":["1.9a1"],"last_affected":[],"package":"django","purl":"pkg:pypi/django","source":"GHSA-6wcr-wcqm-3mfh"},{"ecosystem":"Red Hat:openstack-optools:7::el7","fixed":["0:1.6.11-4.el7ost"],"introduced":["0"],"last_affected":[],"package":"python-django","purl":"pkg:rpm/redhat/python-django","source":"RHSA-2016:0360"},{"ecosystem":"Red Hat:openstack-optools:7::el7","fixed":["0:1.6.11-4.el7ost"],"introduced":["0"],"last_affected":[],"package":"python-django-bash-completion","purl":"pkg:rpm/redhat/python-django-bash-completion","source":"RHSA-2016:0360"},{"ecosystem":"Red Hat:openstack:5::el6","fixed":["0:1.6.11-4.el6ost"],"introduced":["0"],"last_affected":[],"package":"python-django","purl":"pkg:rpm/redhat/python-django","source":"RHSA-2016:0158"},{"ecosystem":"Red Hat:openstack:5::el6","fixed":["0:1.6.11-4.el6ost"],"introduced":["0"],"last_affected":[],"package":"python-django-bash-completion","purl":"pkg:rpm/redhat/python-django-bash-completion","source":"RHSA-2016:0158"},{"ecosystem":"Red Hat:openstack:5::el6","fixed":["0:1.6.11-4.el6ost"],"introduced":["0"],"last_affected":[],"package":"python-django-doc","purl":"pkg:rpm/redhat/python-django-doc","source":"RHSA-2016:0158"},{"ecosystem":"Red Hat:openstack:5::el7","fixed":["0:1.6.11-4.el7ost"],"introduced":["0"],"last_affected":[],"package":"python-django","purl":"pkg:rpm/redhat/python-django","source":"RHSA-2016:0157"},{"ecosystem":"Red Hat:openstack:5::el7","fixed":["0:1.6.11-4.el7ost"],"introduced":["0"],"last_affected":[],"package":"python-django-bash-completion","purl":"pkg:rpm/redhat/python-django-bash-completion","source":"RHSA-2016:0157"},{"ecosystem":"Red Hat:openstack:5::el7","fixed":["0:1.6.11-4.el7ost"],"introduced":["0"],"last_affected":[],"package":"python-django-doc","purl":"pkg:rpm/redhat/python-django-doc","source":"RHSA-2016:0157"},{"ecosystem":"Red Hat:openstack:6::el7","fixed":["0:1.6.11-4.el7ost"],"introduced":["0"],"last_affected":[],"package":"python-django","purl":"pkg:rpm/redhat/python-django","source":"RHSA-2016:0129"},{"ecosystem":"Red Hat:openstack:6::el7","fixed":["0:1.6.11-4.el7ost"],"introduced":["0"],"last_affected":[],"package":"python-django-bash-completion","purl":"pkg:rpm/redhat/python-django-bash-completion","source":"RHSA-2016:0129"},{"ecosystem":"Red Hat:openstack:6::el7","fixed":["0:1.6.11-4.el7ost"],"introduced":["0"],"last_affected":[],"package":"python-django-doc","purl":"pkg:rpm/redhat/python-django-doc","source":"RHSA-2016:0129"},{"ecosystem":"Red Hat:openstack:7::el7","fixed":["0:1.8.7-1.el7"],"introduced":["0"],"last_affected":[],"package":"python-django","purl":"pkg:rpm/redhat/python-django","source":"RHSA-2016:0156"},{"ecosystem":"Red Hat:openstack:7::el7","fixed":["0:1.8.7-1.el7"],"introduced":["0"],"last_affected":[],"package":"python-django-bash-completion","purl":"pkg:rpm/redhat/python-django-bash-completion","source":"RHSA-2016:0156"},{"ecosystem":"Red Hat:openstack:7::el7","fixed":["0:1.8.7-1.el7"],"introduced":["0"],"last_affected":[],"package":"python-django-doc","purl":"pkg:rpm/redhat/python-django-doc","source":"RHSA-2016:0156"},{"ecosystem":"SUSE:Enterprise Storage 1.0","fixed":["1.6.11-11.1"],"introduced":["0"],"last_affected":[],"package":"python-Django","purl":"pkg:rpm/suse/python-Django\u0026distro=SUSE%20Enterprise%20Storage%201.0","source":"SUSE-SU-2015:2327-1"},{"ecosystem":"SUSE:OpenStack Cloud 5","fixed":["1.6.11-13.1"],"introduced":["0"],"last_affected":[],"package":"python-Django","purl":"pkg:rpm/suse/python-Django\u0026distro=SUSE%20OpenStack%20Cloud%205","source":"SUSE-SU-2016:0040-1"}],"prev":{"headline":"Command injection in n/a","id":"CVE-2015-8212"},"products":["n/a"],"published":"2015-12-07","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":"CC BY 4.0","name":"Red Hat","prefix":"RHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"SUSE","prefix":"SUSE"},{"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 obtain sensitive application secrets like SECRET_KEY by manipulating date/time format settings in Django.","url":"https://insights.sbomify.com/CVE-2015-8213/"}