Overview 210 matches · 0 in Waratek scope · 0 protected · 1 exploited · 0 CISA KEV · 13 public PoC · 5 EPSS ≥ 0.5
210matches
0in Waratek scope0.0%
0protected0.0%
1exploited0.5%
0CISA KEV0.0%
13public PoC6.2%
5EPSS ≥ 0.52.4%
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
6
2.9%
Not applicable
204
97.1%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
210
100.0%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 29 / year
20074
Not applicable4
High1
Medium2
Low1
not blocked4
No public exploit4
20082
Not applicable2
Medium2
not blocked2
No public exploit2
20092
Not applicable2
Medium2
not blocked2
No public exploit2
20101
Not applicable1
Medium1
not blocked1
No public exploit1
201110
Not applicable10
High1
Medium9
not blocked10
No public exploit10
20124
Not applicable4
Medium4
not blocked4
No public exploit4
20136
Not applicable6
Medium6
not blocked6
No public exploit6
20149
Not applicable9
High1
Medium7
Low1
not blocked9
Proof of concept only1
No public exploit8
201515
Not applicable15
High2
Medium13
not blocked15
No public exploit15
20167
Not applicable7
Critical1
High3
Medium2
Low1
not blocked7
Working exploit published1
No public exploit6
20176
Not applicable6
Critical1
High1
Medium4
not blocked6
Working exploit published1
No public exploit5
20188
Not applicable8
Critical1
High3
Medium4
not blocked8
Working exploit published1
No public exploit7
201913
Not applicable13
Critical3
High5
Medium5
not blocked13
Working exploit published1
No public exploit12
202013
Outside Waratek scope3
Not applicable10
Critical2
High6
Medium4
Low1
not blocked13
Working exploit published1
Proof of concept only1
No public exploit11
202117
Outside Waratek scope3
Not applicable14
Critical3
High4
Medium9
Low1
not blocked17
Working exploit published1
Proof of concept only1
No public exploit15
202219
Not applicable19
Critical5
High7
Medium7
not blocked19
Working exploit published1
Proof of concept only2
No public exploit16
202313
Not applicable13
Critical2
High6
Medium5
not blocked13
Proof of concept only3
Forecast only2
No public exploit8
202418
Not applicable18
Critical3
High10
Medium5
not blocked18
Proof of concept only1
No public exploit17
202514
Not applicable14
Critical2
High6
Medium6
not blocked14
Working exploit published1
Proof of concept only2
No public exploit11
202629
Not applicable29
Critical1
High9
Medium8
Low11
not blocked29
Exploited1
No public exploit28
2008201020122014201620182020202220242026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2010-4534 | Medium | 2011-01-10 | Not applicable | No public exploit | The administrative interface in django.contrib.admin in Django before 1.1.3, 1.2.x before 1.2.4, and 1.3.x before 1.3 beta 1 does not properly restrict use of the query string to perform certain object filtering, which allows remote authenticated users to obtain sensitive information via a series of requests containing regular expressions, as demonstrated by a created_by__password__regex parameter. |
| CVE-2010-3082 | Medium | 2010-09-14 | Not applicable | No public exploit | Cross-site scripting (XSS) vulnerability in Django 1.2.x before 1.2.2 allows remote attackers to inject arbitrary web script or HTML via a csrfmiddlewaretoken (aka csrf_token) cookie. |
| CVE-2009-3695 | Medium | 2009-10-13 | Not applicable | No public exploit | Algorithmic complexity vulnerability in the forms library in Django 1.0 before 1.0.4 and 1.1 before 1.1.1 allows remote attackers to cause a denial of service (CPU consumption) via a crafted (1) EmailField (email address) or (2) URLField (URL) that triggers a large amount of backtracking in a regular expression. |
| CVE-2009-2659 | Medium | 2009-08-04 | Not applicable | No public exploit | The Admin media handler in core/servers/basehttp.py in Django 1.0 and 0.96 does not properly map URL requests to expected "static media files," which allows remote attackers to conduct directory traversal attacks and read arbitrary files via a crafted URL. |
| CVE-2008-3909 | Medium | 2008-09-04 | Not applicable | No public exploit | The administration application in Django 0.91, 0.95, and 0.96 stores unauthenticated HTTP POST requests and processes them after successful authentication occurs, which allows remote attackers to conduct cross-site request forgery (CSRF) attacks and delete or modify data via unspecified requests. |
| CVE-2008-2302 | Medium | 2008-05-23 | Not applicable | No public exploit | Cross-site scripting (XSS) vulnerability in the login form in the administration application in Django 0.91 before 0.91.2, 0.95 before 0.95.3, and 0.96 before 0.96.2 allows remote attackers to inject arbitrary web script or HTML via the URI of a certain previous request. |
| CVE-2007-5828 | Medium | 2007-11-05 | Not applicable | No public exploit | Cross-site request forgery (CSRF) vulnerability in the admin panel in Django 0.96 allows remote attackers to change passwords of arbitrary users via a request to admin/auth/user/1/password/. NOTE: this issue has been disputed by Debian, since product documentation includes a recommendation for a CSRF protection module that is included with the product. However, CVE considers this an issue because the default configuration does not use this module |
| CVE-2007-5712 | Low | 2007-10-30 | Not applicable | No public exploit | The internationalization (i18n) framework in Django 0.91, 0.95, 0.95.1, and 0.96, and as used in other products such as PyLucid, when the USE_I18N option and the i18n component are enabled, allows remote attackers to cause a denial of service (memory consumption) via many HTTP requests with large Accept-Language headers. |
| CVE-2007-0405 | Medium | 2007-01-23 | Not applicable | No public exploit | The LazyUser class in the AuthenticationMiddleware for Django 0.95 does not properly cache the user name across requests, which allows remote authenticated users to gain the privileges of a different user. |
| CVE-2007-0404 | High | 2007-01-23 | Not applicable | No public exploit | bin/compile-messages.py in Django 0.95 does not quote argument strings before invoking the msgfmt program through the os.system function, which allows attackers to execute arbitrary commands via shell metacharacters in a (1) .po or (2) .mo file. |