Overview 13 matches · 0 in Waratek scope · 0 protected · 1 exploited · 0 CISA KEV · 3 EPSS ≥ 0.5
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
0
0.0%
Outside Waratek scope
1
7.7%
Not applicable
12
92.3%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
13
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
1
7.7%
Working exploit published
8
61.5%
Proof of concept only
4
30.8%
Forecast only
0
0.0%
No public exploit
0
0.0%
split by
peak 2 / year
20141
Not applicable1
Medium1
not blocked1
Proof of concept only1
20150
20161
Not applicable1
Medium1
not blocked1
Working exploit published1
20171
Not applicable1
Medium1
not blocked1
Working exploit published1
20181
Not applicable1
Medium1
not blocked1
Working exploit published1
20191
Not applicable1
Critical1
not blocked1
Working exploit published1
20202
Outside Waratek scope1
Not applicable1
Critical1
High1
not blocked2
Working exploit published1
Proof of concept only1
20211
Not applicable1
Critical1
not blocked1
Working exploit published1
20222
Not applicable2
Critical2
not blocked2
Working exploit published1
Proof of concept only1
20230
20240
20252
Not applicable2
Critical1
High1
not blocked2
Working exploit published1
Proof of concept only1
20261
Not applicable1
High1
not blocked1
Exploited1
2014201620182020202220242026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-1207 | High | 2026-02-03 | Not applicable | Exploited | An issue was discovered in 6.0 before 6.0.2, 5.2 before 5.2.11, and 4.2 before 4.2.28. Raster lookups on ``RasterField`` (only implemented on PostGIS) allows remote attackers to inject SQL via the band index parameter. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Tarek Nakkouch for reporting this issue. |
| CVE-2025-64459 | Critical | 2025-11-05 | Not applicable | Working exploit published | An issue was discovered in 5.1 before 5.1.14, 4.2 before 4.2.26, and 5.2 before 5.2.8. The methods `QuerySet.filter()`, `QuerySet.exclude()`, and `QuerySet.get()`, and the class `Q()`, are subject to SQL injection when using a suitably crafted dictionary, with dictionary expansion, as the `_connector` argument. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank cyberstan for reporting this issue. |
| CVE-2025-57833 | High | 2025-09-03 | Not applicable | Proof of concept only | An issue was discovered in Django 4.2 before 4.2.24, 5.1 before 5.1.12, and 5.2 before 5.2.6. FilteredRelation is subject to SQL injection in column aliases, using a suitably crafted dictionary, with dictionary expansion, as the **kwargs passed QuerySet.annotate() or QuerySet.alias(). |
| CVE-2022-34265 | Critical | 2022-07-04 | Not applicable | Working exploit published | An issue was discovered in Django 3.2 before 3.2.14 and 4.0 before 4.0.6. The Trunc() and Extract() database functions are subject to SQL injection if untrusted data is used as a kind/lookup_name value. Applications that constrain the lookup name and kind choice to a known safe list are unaffected. |
| CVE-2022-28346 | Critical | 2022-04-12 | Not applicable | Proof of concept only | An issue was discovered in Django 2.2 before 2.2.28, 3.2 before 3.2.13, and 4.0 before 4.0.4. QuerySet.annotate(), aggregate(), and extra() methods are subject to SQL injection in column aliases via a crafted dictionary (with dictionary expansion) as the passed **kwargs. |
| CVE-2021-35042 | Critical | 2021-07-02 | Not applicable | Working exploit published | Django 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 web application. |
| CVE-2020-9402 | High | 2020-03-05 | Outside Waratek scope | Working exploit published | Django 1.11 before 1.11.29, 2.2 before 2.2.11, and 3.0 before 3.0.4 allows SQL Injection if untrusted data is used as a tolerance parameter in GIS functions and aggregates on Oracle. By passing a suitably crafted tolerance to GIS functions and aggregates on Oracle, it was possible to break escaping and inject malicious SQL. |
| CVE-2020-7471 | Critical | 2020-02-03 | Not applicable | Proof of concept only | Django 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 (e.g., in Django applications that offer downloads of data as a series of rows with a user-specified column delimiter). By passing a suitably crafted delimiter to a contrib.postgres.aggregates.StringAgg instance, it was possible to break escaping and inject malicious SQL. |
| CVE-2019-19844 | Critical | 2019-12-18 | Not applicable | Working exploit published | Django before 1.11.27, 2.x before 2.2.9, and 3.x before 3.0.1 allows account takeover. A suitably crafted email address (that is equal to an existing user's email address after case transformation of Unicode characters) would allow an attacker to be sent a password reset token for the matched user account. (One mitigation in the new releases is to send password reset tokens only to the registered user email address.) |
| CVE-2018-14574 | Medium | 2018-08-03 | Not applicable | Working exploit published | django.middleware.common.CommonMiddleware in Django 1.11.x before 1.11.15 and 2.0.x before 2.0.8 has an Open Redirect. |
| CVE-2017-12794 | Medium | 2017-09-07 | Not applicable | Working exploit published | In Django 1.10.x before 1.10.8 and 1.11.x before 1.11.5, HTML autoescaping was disabled in a portion of the template for the technical 500 debug page. Given the right circumstances, this allowed a cross-site scripting attack. This vulnerability shouldn't affect most production sites since you shouldn't run with "DEBUG = True" (which makes this page accessible) in your production settings. |
| CVE-2016-6186 | Medium | 2016-08-05 | Not applicable | Working exploit published | Cross-site scripting (XSS) vulnerability in the dismissChangeRelatedObjectPopup function in contrib/admin/static/admin/js/admin/RelatedObjectLookups.js in Django before 1.8.14, 1.9.x before 1.9.8, and 1.10.x before 1.10rc1 allows remote attackers to inject arbitrary web script or HTML via vectors involving unsafe usage of Element.innerHTML. |
| CVE-2014-0472 | Medium | 2014-04-23 | Not applicable | Proof of concept only | The django.core.urlresolvers.reverse function 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 allows remote attackers to import and execute arbitrary Python modules by leveraging a view that constructs URLs using user input and a "dotted Python path." |