Is django 1.1 vulnerable?
PyPI · 2 releases from 1.1.3 to 1.1.4 · latest django is 6.1.3 · checked 18 Nov 2026
Yes: 43 known advisories
Yes. django 1.1.4, the last 1.1 release, is affected by 43 known security advisories (5 critical, 18 high, 15 medium, 5 low), including CVE-2025-64459, CVE-2012-3442, CVE-2014-0472. 3 more affect earlier 1.1.x releases. At least one has no fixed release yet.
Is your project on an affected django?
Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting django 1.1.4
Django GeoDjango spatial lookups allow file writes and outbound requests through GDAL raster parsing
- Affected
- <5.2.17 · >=6.0a1 <6.0.8
- Fixed in
- 5.2.17, 6.0.8
Django GeoDjango vulnerable to denial of service through deeply nested geometry collections
- Affected
- <5.2.17 · >=6.0a1 <6.0.8 · >=6.1a1 <6.1.1
- Fixed in
- 5.2.17, 6.0.8, 6.1.1
Django: DomainNameValidator permits newline characters that may enable HTTP header injection
- Affected
- <5.2.16 · >=6.0.0 <6.0.7
- Fixed in
- 5.2.16, 6.0.7
Django: GDALRaster may over-read heap memory when constructed from bytes
- Affected
- <5.2.16 · >=6.0.0 <6.0.7
- Fixed in
- 5.2.16, 6.0.7
Django: cache middleware may expose private responses when unrelated request cookies are present
- Affected
- <5.2.16 · >=6.0.0 <6.0.7
- Fixed in
- 5.2.16, 6.0.7
Django: UpdateCacheMiddleware may disclose cached responses due to case-sensitive Cache-Control handling
- Affected
- <5.2.15 · >=6.0.0 <6.0.6
- Fixed in
- 5.2.15, 6.0.6
Django: has_vary_header may expose cached responses when Vary values contain whitespace
- Affected
- <5.2.15 · >=6.0.0 <6.0.6
- Fixed in
- 5.2.15, 6.0.6
Django: signed cookies are vulnerable to salt namespace collisions
- Affected
- <5.2.15 · >=6.0.0 <6.0.6
- Fixed in
- 5.2.15, 6.0.6
Django vulnerable to SQL injection via _connector keyword argument in QuerySet and Q objects.
- Affected
- >=5.2a1 <5.2.8 · >=5.0a1 <5.1.14 · <4.2.26
- Fixed in
- 4.2.26, 5.1.14, 5.2.8
Django has a denial-of-service vulnerability in HttpResponseRedirect and HttpResponsePermanentRedirect on Windows
- Affected
- >=5.2a1 <5.2.8 · >=5.0a1 <5.1.14 · <4.2.26
- Fixed in
- 4.2.26, 5.1.14, 5.2.8
Django is subject to SQL injection through its column aliases
- Affected
- <4.2.24 · >=5.0a1 <5.1.12 · >=5.2a1 <5.2.6
- Fixed in
- 4.2.24, 5.1.12, 5.2.6
Django Improper Output Neutralization for Logs vulnerability
- Affected
- >=5.2 <5.2.2 · >=5.0a1 <5.1.10 · <4.2.22
- Fixed in
- 4.2.22, 5.1.10, 5.2.2
Django allows enumeration of user e-mail addresses
- Affected
- >=5.1 <5.1.1 · >=5.0 <5.0.9 · <4.2.16
- Fixed in
- 4.2.16, 5.0.9, 5.1.1
Django vulnerable to Reflected File Download attack
- Affected
- <3.2.15 · >=4.0 <4.0.7
- Fixed in
- 3.2.15, 4.0.7
Django Allows Redirect via Data URL
- Affected
- <1.3.2 · >=1.4 <1.4.1
- Fixed in
- 1.3.2, 1.4.1
Django Image Field Vulnerable to Image Decompression Bombs
- Affected
- <1.3.2 · >=1.4 <1.4.1
- Fixed in
- 1.3.2, 1.4.1
Django vulnerable to Improper Restriction of Operations within the Bounds of a Memory Buffer
- Affected
- <1.3.2 · >=1.4 <1.4.1
- Fixed in
- 1.3.2, 1.4.1
Django Cross-site Scripting Vulnerability
- Affected
- <1.7.6 · >=1.8a1 <1.8b2
- Fixed in
- 1.7.6, 1.8b2
Django WSGI Header Spoofing Vulnerability
- Affected
- <1.4.18 · >=1.6 <1.6.10 · >=1.7 <1.7.3
- Fixed in
- 1.4.18, 1.6.10, 1.7.3
Django DoS in django.views.static.serve
- Affected
- <1.4.18 · >=1.6 <1.6.10 · >=1.7 <1.7.3
- Fixed in
- 1.4.18, 1.6.10, 1.7.3
Django Cross-site Scripting Vulnerability
- Affected
- <1.4.18 · >=1.6 <1.6.10 · >=1.7 <1.7.3
- Fixed in
- 1.4.18, 1.6.10, 1.7.3
Code Injection in Django
- Affected
- <1.4.11 · >=1.5 <1.5.6 · >=1.6 <1.6.3
- Fixed in
- 1.4.11, 1.5.6, 1.6.3
Django Reuses Cached CSRF Token
- Affected
- <1.4.11 · >=1.5 <1.5.6 · >=1.6 <1.6.3
- Fixed in
- 1.4.11, 1.5.6, 1.6.3
Django Vulnerable to MySQL Injection
- Affected
- <1.4.11 · >=1.5 <1.5.6 · >=1.6 <1.6.3
- Fixed in
- 1.4.11, 1.5.6, 1.6.3
Django XSS Vulnerability
- Affected
- <1.8.10 · >=1.9a1 <1.9.3
- Fixed in
- 1.8.10, 1.9.3
Django User Enumeration Vulnerability
- Affected
- <1.8.10 · >=1.9 <1.9.3
- Fixed in
- 1.8.10, 1.9.3
Django Vulnerable to HTTP Response Splitting Attack
- Affected
- <1.4.21 · >=1.5 <1.7.9 · >=1.8a1 <1.8.3
- Fixed in
- 1.4.21, 1.7.9, 1.8.3
Django CSRF Protection Bypass
- Affected
- <1.8.15 · >=1.9 <1.9.10
- Fixed in
- 1.8.15, 1.9.10
Django Vulnerable to Cache Poisoning
- Affected
- <1.2.7 · >=1.3 <1.3.1
- Fixed in
- 1.2.7, 1.3.1
Django Might Allow CSRF Requests via URL Verification
- Affected
- <1.2.7 · >=1.3 <1.3.1
- Fixed in
- 1.2.7, 1.3.1
Django Cross-site scripting Vulnerability
- Affected
- <1.8.14 · >=1.9 <1.9.8 · >=1.10a1 <1.10rc1
- Fixed in
- 1.8.14, 1.9.8, 1.10rc1
Django Incorrectly Validates URLs
- Affected
- <1.4.14 · >=1.5 <1.5.9 · >=1.6 <1.6.6
- Fixed in
- 1.4.14, 1.5.9, 1.6.6
Django Middleware Enables Session Hijacking
- Affected
- <1.4.14 · >=1.5 <1.5.9 · >=1.6 <1.6.6 · >=1.7a1 <1.7c3
- Fixed in
- 1.4.14, 1.5.9, 1.6.6, 1.7c3
Django data leakage via querystring manipulation in admin
- Affected
- <1.4.14 · >=1.5 <1.5.9 · >=1.6 <1.6.6 · >=1.7a1 <1.7c3
- Fixed in
- 1.4.14, 1.5.9, 1.6.6, 1.7c3
Django cross-site scripting (XSS) attack via user-supplied redirect URLs
- Affected
- <1.4.20 · >=1.5 <1.6.11 · >=1.7 <1.7.7 · >=1.8a1 <1.8c1
- Fixed in
- 1.4.20, 1.6.11, 1.7.7, 1.8c1
Django denial of service via file upload naming
- Affected
- <1.4.14 · >=1.5 <1.5.9 · >=1.6 <1.6.6
- Fixed in
- 1.4.14, 1.5.9, 1.6.6
Path Traversal in Django
- Affected
- <2.2.24 · >=3.0 <3.1.12 · >=3.2 <3.2.4
- Fixed in
- 2.2.24, 3.1.12, 3.2.4
SQL injection in Django
- Affected
- <1.11.28 · >=2.0 <2.2.10 · >=3.0 <3.0.3
- Fixed in
- 1.11.28, 2.2.10, 3.0.3
Django Potential account hijack via password reset form
- Affected
- <1.11.27 · >=2.0 <2.2.9 · >=3.0 <3.0.1
- Fixed in
- 1.11.27, 2.2.9, 3.0.1
Django Denial-of-service by filling session store
- Affected
- <1.4.21 · >=1.5 <1.7.9 · >=1.8 <1.8.3
- Fixed in
- 1.4.21, 1.7.9, 1.8.3
Session manipulation in Django
- Affected
- <1.2.7 · >=1.3 <1.3.1
- Fixed in
- 1.2.7, 1.3.1
Denial of service in django
- Affected
- <1.2.7 · >=1.3 <1.3.1
- Fixed in
- 1.2.7, 1.3.1
Django Cross-Site Request Forgery vulnerability
- Affected
- <=1.2.7 · >=1.3 <=1.3.1
- Fixed in
- No fix released
Fixed within 1.1.x, affecting earlier releases
Cross-site scripting in django
- Affected
- >=1.1 <1.1.4 · >=1.2 <1.2.5
- Fixed in
- 1.1.4, 1.2.5
Directory traversal in Django
- Affected
- >=1.1 <1.1.4 · >=1.2 <1.2.5
- Fixed in
- 1.1.4, 1.2.5
Cross-site request forgery in Django
- Affected
- >=1.1 <1.1.4 · >=1.2 <1.2.5
- Fixed in
- 1.1.4, 1.2.5
Every django 1.1.x release
Affected: 1.1.3 to 1.1.4. Latest django: 6.1.3.
| Version | Known advisories |
|---|---|
| django 1.1.4 | CVE-2026-15307, CVE-2026-15830, CVE-2026-53878, CVE-2026-53877, CVE-2026-48588, CVE-2026-8404, CVE-2026-48587, CVE-2026-6873, CVE-2025-64459, CVE-2025-64458, CVE-2025-57833, CVE-2025-48432, CVE-2024-45231, CVE-2022-36359, CVE-2012-3442, CVE-2012-3443, CVE-2012-3444, CVE-2015-2241, CVE-2015-0219, CVE-2015-0221, CVE-2015-0220, CVE-2014-0472, CVE-2014-0473, CVE-2014-0474, CVE-2016-2512, CVE-2016-2513, CVE-2015-5144, CVE-2016-7401, CVE-2011-4139, CVE-2011-4138, CVE-2016-6186, CVE-2014-0480, CVE-2014-0482, CVE-2014-0483, CVE-2015-2317, CVE-2014-0481, CVE-2021-33203, CVE-2020-7471, CVE-2019-19844, CVE-2015-5143, CVE-2011-4136, CVE-2011-4137, CVE-2011-4140 |
| django 1.1.3 | CVE-2026-15307, CVE-2026-15830, CVE-2026-53878, CVE-2026-53877, CVE-2026-48588, CVE-2026-8404, CVE-2026-48587, CVE-2026-6873, CVE-2025-64459, CVE-2025-64458, CVE-2025-57833, CVE-2025-48432, CVE-2024-45231, CVE-2022-36359, CVE-2012-3442, CVE-2012-3443, CVE-2012-3444, CVE-2015-2241, CVE-2015-0219, CVE-2015-0221, CVE-2015-0220, CVE-2014-0472, CVE-2014-0473, CVE-2014-0474, CVE-2016-2512, CVE-2016-2513, CVE-2015-5144, CVE-2016-7401, CVE-2011-4139, CVE-2011-4138, CVE-2016-6186, CVE-2014-0480, CVE-2014-0482, CVE-2014-0483, CVE-2015-2317, CVE-2014-0481, CVE-2021-33203, CVE-2020-7471, CVE-2019-19844, CVE-2015-5143, CVE-2011-0697, CVE-2011-4136, CVE-2011-0698, CVE-2011-4137, CVE-2011-4140, CVE-2011-0696 |
Which of your client projects are still on django 1.1?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact django version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other django versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the PyPI registry. Refreshed daily.