How severe is CVE-2015-8213?

CVE-2015-8213 has a CVSS score of 2.8/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2015-8213?

CVE-2015-8213 affects the following packages: django (PyPI), django (PyPI), django (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2015-8213?

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

How do I detect CVE-2015-8213 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-2015-8213 if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is CVE-2015-8213 actively exploited in the wild?

No public exploit code has been indexed for CVE-2015-8213 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-2015-8213?

CVE-2015-8213 has an EPSS (Exploit Prediction Scoring System) score of 4.3%, placing it in the 91th 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.

What type of vulnerability is CVE-2015-8213?

CVE-2015-8213 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2015-8213 published, and has it been updated?

CVE-2015-8213 was published on December 7, 2015 and was last updated on April 16, 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

LOW severity

CVE-2015-8213 — django

LOWFix: django/django@316bc3f

CVE-2015-8213 is a low-severity (CVSS 2.8) Information Exposure vulnerability in django. A fix is available for django — see the affected versions and patch details below.

Django settings leak in date template filter

Also known asGHSA-6wcr-wcqm-3mfhPYSEC-2015-11

Published

Dec 7, 2015

Updated

Apr 16, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

4.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs91th percentile — riskier than 91% of all scored CVEsHighest risk

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected

🐍django🐍django🐍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 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.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`django`	≥ 1.7&&< 1.7.11	1.7.11`pip install --upgrade 'django==1.7.11'`
🐍PyPI	`django`	≥ 1.8a1&&< 1.8.7	1.8.7`pip install --upgrade 'django==1.8.7'`
🐍PyPI	`django`	≥ 1.9a1&&< 1.9rc2	1.9rc2`pip install --upgrade 'django==1.9rc2'`

Affected Products

1 product · 9 configurations

Application

djangodjangoproject

≤ 1.7.10

8 versions

1.8.01.8.11.8.21.8.31.8.41.8.51.8.61.9.0

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.7.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-8213 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Product	Fixed in	Advisory
Red Hat Enterprise Linux OpenStack Platform 5.0 (Icehouse) for RHEL 6	`python-django-0:1.6.11-4.el6ost`	RHSA-2016:0158
Red Hat Enterprise Linux OpenStack Platform 5.0 (Icehouse) for RHEL 7	`python-django-0:1.6.11-4.el7ost`	RHSA-2016:0157
Red Hat Enterprise Linux OpenStack Platform 6.0 (Juno) for RHEL 7	`python-django-0:1.6.11-4.el7ost`	RHSA-2016:0129
Red Hat Enterprise Linux OpenStack Platform 7.0 (Kilo) for RHEL 7	`python-django-0:1.8.7-1.el7`	RHSA-2016:0156
Red Hat Enterprise Linux OpenStack Platform 7.0 Operational Tools for RHEL 7	`python-django-0:1.6.11-4.el7ost`	RHSA-2016:0360

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2015-8213 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works