The caching framework in Django before 1.4.11, 1.5.x before 1.5.6, 1.6.x before 1.6.3, and 1.7.x before 1.7 beta 2 reuses a cached CSRF toke
The caching framework in Django before 1.4.11, 1.5.x before 1.5.6, 1.6.x before 1.6.3, and 1.7.x before 1.7 beta 2 reuses a cached CSRF token for all anonymous users, which allows remote attackers to bypass CSRF protections by reading the CSRF cookie for anonymous users.
- Published
- Apr 23, 2014
- Updated
- Jun 16, 2026
- EPSS
- 2.0% · 80th percentile
- CWE
- CWE-264
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
21
Monitor
Low priority for now.
- CVSS
- 20 / 40 · 5.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.0%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| djangoproject | django | cpe:2.3:a:djangoproject:django |
| canonical | ubuntu linux | cpe:2.3:o:canonical:ubuntu_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- canonical ubuntu linux10.04
- canonical ubuntu linux12.04
- canonical ubuntu linux12.10
- canonical ubuntu linux13.10
- canonical ubuntu linux14.04
- djangoproject djangoup to 1.4.10 inclusive
- djangoproject django1.4
- djangoproject django1.4.1
- djangoproject django1.4.2
- djangoproject django1.4.3
- djangoproject django1.4.4
- djangoproject django1.4.5
- djangoproject django1.4.6
- djangoproject django1.4.7
- djangoproject django1.4.8
- djangoproject django1.4.9
- djangoproject django1.5
- djangoproject django1.5.1
- djangoproject django1.5.2
- djangoproject django1.5.3
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | python-django | before 1.6.3-1 | 1.6.3-1 |
| Debian:6.0 | python-django | before 1.2.3-3+squeeze10 | 1.2.3-3+squeeze10 |
| Debian:7 | python-django | before 1.4.5-1+deb7u7 | 1.4.5-1+deb7u7 |
| PyPI | django | from 1.5 · before 1.5.6 | 1.5.6 |
| PyPI | django | from 1.6 · before 1.6.3 | 1.6.3 |
| PyPI | django | before 1.4.11 | 1.4.11 |
| Red Hat:openstack:4::el6 | Django14 | before 0:1.4.11-1.el6ost | 0:1.4.11-1.el6ost |
| Red Hat:openstack:4::el6 | Django14-doc | before 0:1.4.11-1.el6ost | 0:1.4.11-1.el6ost |
Same product
djangoproject: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-34265An issue was discovered in Django 3.2 before 3.2.14 and 4.0 before 4.0.6.61This week
- CVE-2020-7471Django 1.11 before 1.11.28, 2.2 before 2.2.10, and 3.0 before 3.0.3 allows SQL Injection if untrusted data is used as a StringAgg delimiter 59Plan
- CVE-2019-19844Django before 1.11.27, 2.x before 2.2.9, and 3.x before 3.0.1 allows account takeover.55Plan
- CVE-2019-14234An issue was discovered in Django 1.11.x before 1.11.23, 2.1.x before 2.1.11, and 2.2.x before 2.2.4.53Plan
- CVE-2021-35042Django 3.1.x before 3.1.13 and 3.2.x before 3.2.5 allows QuerySet.order_by SQL injection if order_by is untrusted input from a client of a w52Plan
- CVE-2023-24580An issue was discovered in the Multipart Request Parser in Django 3.2 before 3.2.18, 4.0 before 4.0.10, and 4.1 before 4.1.7.49Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:python-django | 1.6.3-1 · Debian:12 | Package registry (OSV) |
| PyPI:django | 1.4.11 | Package registry (OSV) |
| PyPI:django | 1.5.6 | Package registry (OSV) |
| PyPI:django | 1.6.3 | Package registry (OSV) |
| red hat:Django14 | 0:1.4.11-1.el6ost · Red Hat:openstack:4::el6 | Package registry (OSV) |
| red hat:Django14-doc | 0:1.4.11-1.el6ost · Red Hat:openstack:4::el6 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- P · data can be read
- Integrity
- none
- Availability
- none
- Attack complexity
- Low
- Confidentiality impact
- P
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-264 · Permissions, Privileges, and Access ControlsCVSS vector
AV:N/AC:L/Au:N/C:P/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- lists.opensuse.org/opensuse-updates/2014-09/msg00023.html
- rhn.redhat.com/errata/RHSA-2014-0456.html
- rhn.redhat.com/errata/RHSA-2014-0457.html
- secunia.com/advisories/61281
- www.debian.org/security/2014/dsa-2934
- www.ubuntu.com/usn/USN-2169-1
- www.djangoproject.com/weblog/2014/apr/21/security/
Vendor advisories and official records. Exploit/PoC links are deliberately left out.