django vulnerabilities
A high-level Python web framework that encourages rapid development and clean, pragmatic design.
- Registry
- PyPI
- Latest
- 6.1.3
- License
- BSD-3-Clause
162 known advisories
The latest version, 6.1.3, is not affected by any of them. Projects on older versions may be.
pip install 'django>=6.1.3'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
Security advisories for django
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 fails to prevent reuse of a partially-initialized connection after a failed `STARTTLS` handshake
- Affected
- >=5.2 <5.2.15 · >=6.0 <6.0.6
- Fixed in
- 5.2.15, 6.0.6
Django: UpdateCacheMiddleware may disclose private cached responses by omitting Authorization from Vary
- Affected
- >=5.2.0 <5.2.15 · >=6.0.0 <6.0.6
- Fixed in
- 5.2.15, 6.0.6
Django has an Improper Handling of Length Parameter Inconsistency
- Affected
- >=6.0 <6.0.5 · >=5.2 <5.2.14
- Fixed in
- 5.2.14, 6.0.5
Django Uses Cache Containing Sensitive Information
- Affected
- >=6.0 <6.0.5 · >=5.2 <5.2.14
- Fixed in
- 5.2.14, 6.0.5
Django Uses Persistent Cookies Containing Sensitive Information
- Affected
- >=6.0 <6.0.5 · >=5.2 <5.2.14
- Fixed in
- 5.2.14, 6.0.5
Django vulnerable to ASGI header spoofing via underscore/hyphen conflation
- Affected
- >=6.0 <6.0.4 · >=5.2 <5.2.13 · >=4.2 <4.2.30
- Fixed in
- 4.2.30, 5.2.13, 6.0.4
Django vulnerable to privilege abuse in ModelAdmin.list_editable
- Affected
- >=6.0 <6.0.4 · >=5.2 <5.2.13 · >=4.2 <4.2.30
- Fixed in
- 4.2.30, 5.2.13, 6.0.4
Django vulnerable to privilege abuse in GenericInlineModelAdmin
- Affected
- >=6.0 <6.0.4 · >=5.2 <5.2.13 · >=4.2 <4.2.30
- Fixed in
- 4.2.30, 5.2.13, 6.0.4
Django: SGI requests with a missing or understated `Content-Length` header could bypass the `DATA_UPLOAD_MAX_MEMORY_SIZE` limit
- Affected
- >=6.0 <6.0.4 · >=5.2 <5.2.13 · >=4.2 <4.2.30
- Fixed in
- 4.2.30, 5.2.13, 6.0.4
Django has potential DoS via MultiPartParser through crafted multipart uploads
- Affected
- >=6.0 <6.0.4 · >=5.2 <5.2.13 · >=4.2 <4.2.30
- Fixed in
- 4.2.30, 5.2.13, 6.0.4
Django vulnerable to Uncontrolled Resource Consumption
- Affected
- >=6.0 <6.0.3 · >=5.2 <5.2.12 · >=4.2 <4.2.29
- Fixed in
- 4.2.29, 5.2.12, 6.0.3
Django has a Race Condition vulnerability
- Affected
- >=6.0 <6.0.3 · >=5.2 <5.2.12 · >=4.2 <4.2.29
- Fixed in
- 4.2.29, 5.2.12, 6.0.3
Django has an SQL Injection issue
- Affected
- >=6.0a1 <6.0.2 · >=5.2a1 <5.2.11 · >=4.2a1 <4.2.28
- Fixed in
- 4.2.28, 5.2.11, 6.0.2
Django has an SQL Injection issue
- Affected
- >=6.0a1 <6.0.2 · >=5.2a1 <5.2.11 · >=4.2a1 <4.2.28
- Fixed in
- 4.2.28, 5.2.11, 6.0.2
Django has an SQL Injection issue
- Affected
- >=6.0a1 <6.0.2 · >=5.2a1 <5.2.11 · >=4.2a1 <4.2.28
- Fixed in
- 4.2.28, 5.2.11, 6.0.2
Django has Observable Timing Discrepancy
- Affected
- >=6.0a1 <6.0.2 · >=5.2a1 <5.2.11 · >=4.2a1 <4.2.28
- Fixed in
- 4.2.28, 5.2.11, 6.0.2
Django has Inefficient Algorithmic Complexity
- Affected
- >=6.0a1 <6.0.2 · >=5.2a1 <5.2.11 · >=4.2a1 <4.2.28
- Fixed in
- 4.2.28, 5.2.11, 6.0.2
Django has Inefficient Algorithmic Complexity
- Affected
- >=6.0a1 <6.0.2 · >=5.2a1 <5.2.11 · >=4.2a1 <4.2.28
- Fixed in
- 4.2.28, 5.2.11, 6.0.2
Django is vulnerable to SQL injection in column aliases
- Affected
- >=5.2a1 <5.2.9 · >=5.1a1 <5.1.15 · >=4.2a1 <4.2.27
- Fixed in
- 4.2.27, 5.1.15, 5.2.9
Django is vulnerable to DoS via XML serializer text extraction
- Affected
- >=5.2a1 <5.2.9 · >=5.1a1 <5.1.15 · >=4.2a1 <4.2.27
- Fixed in
- 4.2.27, 5.1.15, 5.2.9
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 vulnerable to partial directory traversal via archives
- Affected
- >=4.2 <4.2.25 · >=5.1 <5.1.13 · >=5.2 <5.2.7
- Fixed in
- 4.2.25, 5.1.13, 5.2.7
Django vulnerable to SQL injection in column aliases
- Affected
- >=4.2 <4.2.25 · >=5.1 <5.1.13 · >=5.2 <5.2.7
- Fixed in
- 4.2.25, 5.1.13, 5.2.7
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 has a denial-of-service possibility in strip_tags()
- Affected
- >=4.2 <4.2.21 · >=5.1 <5.1.9 · >=5.2 <5.2.1
- Fixed in
- 4.2.21, 5.1.9, 5.2.1
Django Potential Denial of Service (DoS) on Windows
- Affected
- >=5.0 <5.0.14 · >=5.1 <5.1.8
- Fixed in
- 5.0.14, 5.1.8
Django Vulnerable to Allocation of Resources Without Limits or Throttling
- Affected
- >=4.2 <4.2.20 · >=5.0 <5.0.13 · >=5.1 <5.1.7
- Fixed in
- 4.2.20, 5.0.13, 5.1.7
Django has a potential denial-of-service vulnerability in IPv6 validation
- Affected
- >=5.1 <5.1.5 · >=5.0 <5.0.11 · >=4.2 <4.2.18 · >=5.1 <5.1.5 · >=5.0 <5.0.11 · >=4.2 <4.2.18
- Fixed in
- 4.2.18, 5.0.11, 5.1.5
Django SQL injection in HasKey(lhs, rhs) on Oracle
- Affected
- >=5.0.0 <5.0.10 · >=5.1.0 <5.1.4 · >=4.2.0 <4.2.17 · >=5.1 <5.1.4 · >=5.0 <5.0.10 · >=4.2 <4.2.17
- Fixed in
- 4.2.17, 5.0.10, 5.1.4
Django denial-of-service in django.utils.html.strip_tags()
- Affected
- >=5.1.0 <5.1.4 · >=4.2.0 <4.2.17 · >=5.0.0 <5.0.10 · >=5.1 <5.1.4 · >=5.0 <5.0.10 · >=4.2 <4.2.17
- Fixed in
- 4.2.17, 5.0.10, 5.1.4
Django vulnerable to denial-of-service attack via the urlize() and urlizetrunc() template filters
- Affected
- >=5.1 <5.1.1 · >=5.0 <5.0.9 · >=4.2 <4.2.16
- Fixed in
- 4.2.16, 5.0.9, 5.1.1
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 SQL injection vulnerability
- Affected
- >=5.0 <5.0.8 · >=4.2 <4.2.15
- Fixed in
- 4.2.15, 5.0.8
Django vulnerable to a denial-of-service attack
- Affected
- >=5.0 <5.0.8 · >=4.2 <4.2.15
- Fixed in
- 4.2.15, 5.0.8
Django memory consumption vulnerability
- Affected
- >=5.0 <5.0.8 · >=4.2 <4.2.15
- Fixed in
- 4.2.15, 5.0.8
Django vulnerable to denial-of-service attack
- Affected
- >=5.0 <5.0.8 · >=4.2 <4.2.15
- Fixed in
- 4.2.15, 5.0.8
Django Path Traversal vulnerability
- Affected
- >=5.0 <5.0.7 · >=4.2 <4.2.14
- Fixed in
- 4.2.14, 5.0.7
Django vulnerable to Denial of Service
- Affected
- >=5.0 <5.0.7 · >=4.2 <4.2.14
- Fixed in
- 4.2.14, 5.0.7
Django vulnerable to Denial of Service
- Affected
- >=4.2 <4.2.14 · >=5.0 <5.0.7
- Fixed in
- 4.2.14, 5.0.7
Django vulnerable to user enumeration attack
- Affected
- >=5.0 <5.0.7 · >=4.2 <4.2.14
- Fixed in
- 4.2.14, 5.0.7
Regular expression denial-of-service in Django
- Affected
- >=3.2 <3.2.25 · >=4.2 <4.2.11 · >=5.0 <5.0.3
- Fixed in
- 3.2.25, 4.2.11, 5.0.3
Django denial-of-service attack in the intcomma template filter
- Affected
- >=3.2 <3.2.24 · >=4.2 <4.2.10 · >=5.0 <5.0.2
- Fixed in
- 3.2.24, 4.2.10, 5.0.2
Django Denial-of-service in django.utils.text.Truncator
- Affected
- >=3.2a1 <3.2.22 · >=4.1a1 <4.1.12 · >=4.2a1 <4.2.6
- Fixed in
- 3.2.22, 4.1.12, 4.2.6
Django Denial of service vulnerability in django.utils.encoding.uri_to_iri
- Affected
- >=3.2 <3.2.21 · >=4.1 <4.1.11 · >=4.2 <4.2.5
- Fixed in
- 3.2.21, 4.1.11, 4.2.5
Django potential denial of service vulnerability in UsernameField on Windows
- Affected
- >=3.2a1 <3.2.23 · >=4.1a1 <4.1.13 · >=4.2a1 <4.2.7
- Fixed in
- 3.2.23, 4.1.13, 4.2.7
Django has regular expression denial of service vulnerability in EmailValidator/URLValidator
- Affected
- >=3.2a1 <3.2.20 · >=4.0a1 <4.1.10 · >=4.2a1 <4.2.3
- Fixed in
- 3.2.20, 4.1.10, 4.2.3
Django bypasses validation when using one form field to upload multiple files
- Affected
- >=3.2a1 <3.2.19 · >=4.0a1 <4.1.9 · >=4.2a1 <4.2.1
- Fixed in
- 3.2.19, 4.1.9, 4.2.1
Resource exhaustion in Django
- Affected
- >=3.2a1 <3.2.18 · >=4.1a1 <4.1.7 · >=4.0a1 <4.0.10
- Fixed in
- 3.2.18, 4.0.10, 4.1.7
Django contains Uncontrolled Resource Consumption via cached header
- Affected
- >=3.2a1 <3.2.17 · >=4.0a1 <4.0.9 · >=4.1a1 <4.1.6
- Fixed in
- 3.2.17, 4.0.9, 4.1.6
Django denial-of-service vulnerability in internationalized URLs
- Affected
- >=3.2 <3.2.16 · >=4.0 <4.0.8 · >=4.1 <4.1.2
- Fixed in
- 3.2.16, 4.0.8, 4.1.2
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 `Trunc()` and `Extract()` database functions vulnerable to SQL Injection
- Affected
- >=3.2a1 <3.2.14 · >=4.0a1 <4.0.6
- Fixed in
- 3.2.14, 4.0.6
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 Allows Arbitrary URL Generation
- Affected
- >=1.3 <1.3.4 · >=1.4 <1.4.2
- Fixed in
- 1.3.4, 1.4.2
XML Entity Expansion (XEE) in Django
- Affected
- >=1.3.0 <1.3.6 · >=1.4.0 <1.4.4
- Fixed in
- 1.3.6, 1.4.4
XML External Entity (XXE) in Django
- Affected
- >=1.3.0 <1.3.6 · >=1.4.0 <1.4.4
- Fixed in
- 1.3.6, 1.4.4
Django Directory Traversal via ssi template tag
- Affected
- >=1.4 <1.4.7 · >=1.5 <1.5.3
- Fixed in
- 1.4.7, 1.5.3
Django Denial of Service Vulnerability in the authentication framework
- Affected
- >=1.4 <1.4.8 · >=1.5 <1.5.4
- Fixed in
- 1.4.8, 1.5.4
Django Access Restrictions Bypass
- Affected
- >=1.9 <1.9.2
- Fixed in
- 1.9.2
Django Cross-site Scripting Vulnerability
- Affected
- <1.7.6 · >=1.8a1 <1.8b2
- Fixed in
- 1.7.6, 1.8b2
Django allows user sessions hijacking via an empty string in the session key
- Affected
- >=1.8a1 <1.8.2
- Fixed in
- 1.8.2
Django settings leak in date template filter
- Affected
- >=1.7 <1.7.11 · >=1.8a1 <1.8.7 · >=1.9a1 <1.9rc2
- Fixed in
- 1.7.11, 1.8.7, 1.9rc2
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 database denial-of-service with ModelMultipleChoiceField
- Affected
- >=1.6 <1.6.10 · >=1.7 <1.7.3
- Fixed in
- 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
Denial-of-service possibility in logout() view by filling session store
- Affected
- >=1.7 <1.7.10 · >=1.4 <1.4.22
- Fixed in
- 1.4.22, 1.7.10
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 Vulnerable to Cache Poisoning
- Affected
- >=1.4 <1.4.13 · >=1.5 <1.5.8 · >=1.6 <1.6.5 · >=1.7a1 <1.7b4
- Fixed in
- 1.4.13, 1.5.8, 1.6.5, 1.7b4
Django cross-site scripting (XSS) vulnerability in the AdminURLFieldWidget widget
- Affected
- >=1.5 <1.5.2
- Fixed in
- 1.5.2
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 ReDoS in validators.URLValidator
- Affected
- >=1.8a1 <1.8.3
- Fixed in
- 1.8.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 denial of service via empty session record creation
- Affected
- >=1.8 <1.8.4 · >=1.7 <1.7.10 · >=1.4 <1.4.22
- Fixed in
- 1.4.22, 1.7.10, 1.8.4
Django DNS Rebinding Vulnerability
- Affected
- >=1.8a1 <1.8.16 · >=1.9a1 <1.9.11 · >=1.10a1 <1.10.3
- Fixed in
- 1.8.16, 1.9.11, 1.10.3
Django user with hardcoded password created when running tests on Oracle
- Affected
- >=1.10a1 <1.10.3 · >=1.9a1 <1.9.11 · >=1.8a1 <1.8.16
- Fixed in
- 1.8.16, 1.9.11, 1.10.3
Django cross-site scripting (XSS) vulnerability via is_safe_url function
- Affected
- >=1.4 <1.4.6 · >=1.5 <1.5.2
- Fixed in
- 1.4.6, 1.5.2
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 Allows Open Redirects
- Affected
- >=1.4 <1.4.13 · >=1.5 <1.5.8 · >=1.6 <1.6.5 · >=1.7a1 <1.7b4
- Fixed in
- 1.4.13, 1.5.8, 1.6.5, 1.7b4
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 Denial-of-service possibility with strip_tags
- Affected
- >=1.6 <1.6.11 · >=1.7 <1.7.7 · >=1.8a1 <1.8c1
- Fixed in
- 1.6.11, 1.7.7, 1.8c1
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
Django Data leakage via admin history log
- Affected
- >=1.3 <1.3.6 · >=1.4 <1.4.4
- Fixed in
- 1.3.6, 1.4.4
Django is vulnerable to Denial of Service attack in formset
- Affected
- >=1.3 <1.3.6 · >=1.4 <1.4.4
- Fixed in
- 1.3.6, 1.4.4
Django Regex Algorithmic Complexity Causes Denial of Service
- Affected
- >=1.0 <1.0.4 · >=1.1 <1.1.1
- Fixed in
- 1.0.4, 1.1.1
Django Admin Media Handler Vulnerable to Directory Traversal
- Affected
- >=0.96.0 <0.96.4 · >=1.0 <1.0.3
- Fixed in
- 0.96.4, 1.0.3
Django cross-site request forgery (CSRF) vulnerability
- Affected
- >=0.91.0 <0.91.3 · >=0.95.0 <0.95.4 · >=0.96.0 <0.96.3
- Fixed in
- 0.91.3, 0.95.4, 0.96.3
Django Cross-site scripting (XSS) vulnerability
- Affected
- >=0.91 <0.91.2 · >=0.95 <0.95.3 · >=0.96 <0.96.2
- Fixed in
- 0.91.2, 0.95.3, 0.96.2
Django vulnerable to Denial of Service via i18n middleware component
- Affected
- >=0.96.0 <0.96.1 · >=0.95 <0.95.2 · >=0.91.0 <0.91.1
- Fixed in
- 0.91.1, 0.95.2, 0.96.1
Django Arbitrary Code Execution
- Affected
- >=0.95 <1.0
- Fixed in
- 1.0
Django Improper Access Control
- Affected
- >=0.95 <1.0
- Fixed in
- 1.0
SQL Injection in Django
- Affected
- >=2.2 <2.2.28 · >=3.2 <3.2.13 · >=4.0 <4.0.4
- Fixed in
- 2.2.28, 3.2.13, 4.0.4
SQL Injection in Django
- Affected
- >=2.2 <2.2.28 · >=3.2 <3.2.13 · >=4.0 <4.0.4
- Fixed in
- 2.2.28, 3.2.13, 4.0.4
Cross-site Scripting in Django
- Affected
- >=2.2 <2.2.27 · >=3.2 <3.2.12 · >=4.0 <4.0.2
- Fixed in
- 2.2.27, 3.2.12, 4.0.2
Infinite Loop in Django
- Affected
- >=2.2 <2.2.27 · >=3.2 <3.2.12 · >=4.0 <4.0.2
- Fixed in
- 2.2.27, 3.2.12, 4.0.2
Information disclosure in Django
- Affected
- >=2.2 <2.2.26 · >=3.2 <3.2.11 · >=4.0 <4.0.1
- Fixed in
- 2.2.26, 3.2.11, 4.0.1
Directory-traversal in Django
- Affected
- >=2.2 <2.2.26 · >=3.2 <3.2.11 · >=4.0 <4.0.1
- Fixed in
- 2.2.26, 3.2.11, 4.0.1
Denial-of-service in Django
- Affected
- >=2.2a1 <2.2.26 · >=3.2a1 <3.2.11 · >=4.0a1 <4.0.1
- Fixed in
- 2.2.26, 3.2.11, 4.0.1
Potential bypass of an upstream access control based on URL paths in Django
- Affected
- >=2.2a1 <2.2.25 · >=3.0a1 <3.1.14 · >=3.2a1 <3.2.10
- Fixed in
- 2.2.25, 3.1.14, 3.2.10
SQL Injection in Django
- Affected
- >=3.2a1 <3.2.5 · >=3.0a1 <3.1.13
- Fixed in
- 3.1.13, 3.2.5
Django Access Control Bypass possibly leading to SSRF, RFI, and LFI attacks
- Affected
- >=2.2a1 <2.2.24 · >=3.0a1 <3.1.12 · >=3.2a1 <3.2.4
- Fixed in
- 2.2.24, 3.1.12, 3.2.4
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
Header injection possible in Django
- Affected
- >=2.2 <2.2.22 · >=3.1 <3.1.10 · >=3.2 <3.2.2
- Fixed in
- 2.2.22, 3.1.10, 3.2.2
Path Traversal in Django
- Affected
- >=2.2 <2.2.21 · >=3.0 <3.1.9 · >=3.2 <3.2.1
- Fixed in
- 2.2.21, 3.1.9, 3.2.1
Directory Traversal in Django
- Affected
- >=2.2a1 <2.2.20 · >=3.0a1 <3.0.14 · >=3.1a1 <3.1.8
- Fixed in
- 2.2.20, 3.0.14, 3.1.8
Django Incorrect Default Permissions
- Affected
- >=2.2a1 <2.2.16 · >=3.0a1 <3.0.10 · >=3.1a1 <3.1.1
- Fixed in
- 2.2.16, 3.0.10, 3.1.1
Django Incorrect Default Permissions
- Affected
- >=2.2 <2.2.16 · >=3.0 <3.0.10 · >=3.1 <3.1.1
- Fixed in
- 2.2.16, 3.0.10, 3.1.1
Django Directory Traversal via archive.extract
- Affected
- >=2.2 <2.2.18 · >=3.1 <3.1.6 · >=3.0 <3.0.12
- Fixed in
- 2.2.18, 3.0.12, 3.1.6
XSS in Django
- Affected
- >=2.2a1 <2.2.13 · >=3.0a1 <3.0.7
- Fixed in
- 2.2.13, 3.0.7
Data leakage via cache key collision in Django
- Affected
- >=2.2 <2.2.13 · >=3.0 <3.0.7
- Fixed in
- 2.2.13, 3.0.7
SQL injection in Django
- Affected
- >=1.11 <1.11.29 · >=2.2 <2.2.11 · >=3.0 <3.0.4
- Fixed in
- 1.11.29, 2.2.11, 3.0.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 allows unintended model editing
- Affected
- >=2.1 <2.1.15 · >=2.2 <2.2.8
- Fixed in
- 2.1.15, 2.2.8
SQL Injection in Django
- Affected
- >=1.11a1 <1.11.23 · >=2.1a1 <2.1.11 · >=2.2a1 <2.2.4
- Fixed in
- 1.11.23, 2.1.11, 2.2.4
Django Denial-of-service in strip_tags()
- Affected
- >=1.11a1 <1.11.23 · >=2.1a1 <2.1.11 · >=2.2a1 <2.2.4
- Fixed in
- 1.11.23, 2.1.11, 2.2.4
Uncontrolled Recursion in Django
- Affected
- >=1.11a1 <1.11.23 · >=2.1a1 <2.1.11 · >=2.2a1 <2.2.4
- Fixed in
- 1.11.23, 2.1.11, 2.2.4
Django Denial-of-service in django.utils.text.Truncator
- Affected
- >=1.11a1 <1.11.23 · >=2.1a1 <2.1.11 · >=2.2a1 <2.2.4
- Fixed in
- 1.11.23, 2.1.11, 2.2.4
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
Django Incorrect HTTP detection with reverse-proxy connecting via HTTPS
- Affected
- >=2.1 <2.1.10 · >=2.2 <2.2.3 · >=1.11 <1.11.22
- Fixed in
- 1.11.22, 2.1.10, 2.2.3
Django Cross-site Scripting in AdminURLFieldWidget
- Affected
- >=1.11a1 <1.11.21 · >=2.1a1 <2.1.9 · >=2.2a1 <2.2.2
- Fixed in
- 1.11.21, 2.1.9, 2.2.2
XSS in jQuery as used in Drupal, Backdrop CMS, and other products
- Affected
- >=2.0a1 <2.1.9 · >=2.2a1 <2.2.2
- Fixed in
- 2.1.9, 2.2.2
Uncontrolled Memory Consumption in Django
- Affected
- >=1.11 <1.11.19 · >=2.0 <2.0.11 · >=2.1 <2.1.6
- Fixed in
- 1.11.19, 2.0.11, 2.1.6
Improper Input Validation in Django
- Affected
- >=1.11a1 <1.11.18 · >=2.0a1 <2.0.10 · >=2.1a1 <2.1.5
- Fixed in
- 1.11.18, 2.0.10, 2.1.5
Django vulnerable to XSS on 500 pages
- Affected
- >=1.10a1 <1.10.8 · >=1.11a1 <1.11.5
- Fixed in
- 1.10.8, 1.11.5
Django open redirect and possible XSS attack via user-supplied numeric redirect URLs
- Affected
- >=1.10a1 <1.10.7 · >=1.9a1 <1.9.13 · >=1.8a1 <1.8.18
- Fixed in
- 1.8.18, 1.9.13, 1.10.7
Django open redirect
- Affected
- >=1.10 <1.10.7 · >=1.9 <1.9.13 · >=1.8 <1.8.18
- Fixed in
- 1.8.18, 1.9.13, 1.10.7
Django denial-of-service possibility in urlize and urlizetrunc template filters
- Affected
- >=2.0a1 <2.0.3 · >=1.11a1 <1.11.11 · >=1.8a1 <1.8.19
- Fixed in
- 1.8.19, 1.11.11, 2.0.3
Django Denial-of-service possibility in truncatechars_html and truncatewords_html template filters
- Affected
- >=2.0 <2.0.3 · >=1.11 <1.11.11 · >=1.8 <1.8.19
- Fixed in
- 1.8.19, 1.11.11, 2.0.3
Django open redirect
- Affected
- >=2.0 <2.0.8 · >=1.11 <1.11.15
- Fixed in
- 1.11.15, 2.0.8
Django vulnerable to information leakage in AuthenticationForm
- Affected
- >=2.0a1 <2.0.2 · >=1.11.8 <1.11.10
- Fixed in
- 1.11.10, 2.0.2
Django allows unprivileged users to read the password hashes of arbitrary accounts
- Affected
- >=2.1 <2.1.2
- Fixed in
- 2.1.2
Cross-site scripting in django
- Affected
- >=1.1 <1.1.4 · >=1.2 <1.2.5
- Fixed in
- 1.1.4, 1.2.5
Cross-site scripting in django
- Affected
- >=1.2 <1.2.2
- Fixed in
- 1.2.2
Session manipulation in Django
- Affected
- <1.2.7 · >=1.3 <1.3.1
- Fixed in
- 1.2.7, 1.3.1
Directory traversal in Django
- Affected
- >=1.1 <1.1.4 · >=1.2 <1.2.5
- Fixed in
- 1.1.4, 1.2.5
Improper date handling in Django
- Affected
- <1.1.3 · >=1.2 <1.2.4
- Fixed in
- 1.1.3, 1.2.4
Improper query string handling in Django
- Affected
- <1.1.3 · >=1.2 <1.2.4
- Fixed in
- 1.1.3, 1.2.4
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
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
Is your django version vulnerable?
Which of your client projects still run an old django?
NPMscan reads the requirements.txt, poetry.lock, uv.lock and Pipfile.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other PyPI packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the PyPI registry.