🛡️ CVE-2016-7401 — django
Description
Django CSRF Protection Bypass
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.
How this vulnerability can be exploited
This issue can be reached over the network, attack complexity is low, an attacker needs no privileges on the target. No user interaction is required. Rated impact: confidentiality none, integrity high, availability none.
Affected software
CVE-2016-7401 is recorded against 1 package.
- django (from 1.9 up to 1.9.10)
Timeline and source
Published on 14 May 2022 and last revised on 28 November 2024. No public exploit is currently recorded for this entry. Record sourced from OSV.
References
nvd.nist.gov (Advisory)
github.com (Web)
github.com (Web)
github.com (Web)
github.com (Package)
github.com (Web)
web.archive.org (Web)
web.archive.org (Web)
www.djangoproject.com (Web)
rhn.redhat.com (Web)
rhn.redhat.com (Web)
rhn.redhat.com (Web)
rhn.redhat.com (Web)
rhn.redhat.com (Web)
rhn.redhat.com (Web)
Details
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| django | 1.9 | 1.9.10 |
References
Similar Threats
- Unknown CLSA-2025-1753747897
- Unknown CLSA-2025-1754352700
- Unknown CLSA-2025-1754352704
- Unknown CLSA-2025-1754352705
- Unknown CLSA-2025-1755821485
More CVE 2016 advisories
Browse all of CVE 2016 in the advisory index.
Site Security Check
Is django part of your stack?
CVE-2016-7401 is rated CVSS 8.0 High. BotEraser scans your installation against known CVE records and tells you whether this vulnerability applies to the versions you actually run.
Scan My Site Free →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.