Skip to main content
No exploitation reportedFix available

CVE-2016-7401

No exploitation reported by the sources we read.

  • Published2016-10-03
  • WeaknessCWE-254

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

The cookie parsing code in Django before 1.8.15 and 1.9.x before 1.9.10, when used on a site with Google Analytics, allows remote attackers to bypass an intended CSRF protection mechanism by setting arbitrary cookies.

Timeline

dates in UTC
  1. 2016-10-0318:59CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 21:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2016-7401?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2016-7401?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD · OSV
Django
BranchAffectedFixed in
1.8≤ 1.8.14no fix published
1.9= 1.9.0no fix published
1.9= 1.9.1no fix published
1.9= 1.9.2no fix published
1.9= 1.9.3no fix published
1.9= 1.9.4no fix published
1.9= 1.9.5no fix published
1.9= 1.9.6no fix published
1.9= 1.9.7no fix published
1.9= 1.9.8no fix published
1.9= 1.9.9no fix published
Canonical ubuntu linux
BranchAffectedFixed in
12.4= 12.04no fix published
14.4= 14.04no fix published
16.4= 16.04no fix published
Django
BranchAffectedFixed in
1.9≥ 1.9, < 1.9.101.9.10
1.8< 1.8.151.8.15

1 more product in the sources.

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

  • NVDCVSS 3.07.5read 2026-10-23
  • NVDCVSS 2.05read 2026-10-23
  • NVDweakness (CWE)CWE-254read 2026-10-23
  • FIRST EPSSEPSS score5.7 %2026-10-23
  • OSVaffected packages—

Technical details

CVSS v3 Vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Published
2016-10-03
Last Modified
2026-06-17
NVD status
Modified

Frequently asked questions

What is CVE-2016-7401?

The cookie parsing code in Django before 1.8.15 and 1.9.x before 1.9.10, when used on a site with Google Analytics, allows remote attackers to bypass an intended CSRF protection mechanism by setting arbitrary cookies.

Is CVE-2016-7401 actively exploited?

Active exploitation of CVE-2016-7401 has not been confirmed. Its EPSS score was 5.7% on 2026-10-23, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2016-7401?

CVE-2016-7401 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N.

Running Django? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month