Djangoproject vulnerabilitiesNone on the known-exploited list.
Djangoproject has 126 published vulnerabilities across 4 products in our catalogue. None of them is on the list of flaws known to be exploited today. The most affected product is Django, with 123. If you run Djangoproject software, patch the exploited flaws first.
We keep watching the known-exploited list.
Which Djangoproject vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Djangoproject's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Djangoproject flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 74%CVE-2022-34265Critical
An issue was discovered in Django 3.2 before 3.2.14 and 4.0 before 4.0.6.
- 66%CVE-2020-7471Critical
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...
- 63%CVE-2023-24580High
An issue was discovered in the Multipart Request Parser in Django 3.2 before 3.2.18, 4.0 before 4.0.10, and 4.1 before 4.1.7.
- 54%CVE-2019-19844Critical
Django before 1.11.27, 2.x before 2.2.9, and 3.x before 3.0.1 allows account takeover.
- 50%CVE-2023-46695High
An issue was discovered in Django 3.2 before 3.2.23, 4.1 before 4.1.13, and 4.2 before 4.2.7.
- 50%CVE-2022-23833High
An issue was discovered in MultiPartParser in Django 2.2 before 2.2.27, 3.2 before 3.2.12, and 4.0 before 4.0.2.
- 48%CVE-2019-14234Critical
An issue was discovered in Django 1.11.x before 1.11.23, 2.1.x before 2.1.11, and 2.2.x before 2.2.4.
- 47%CVE-2023-23969High
In Django 3.2 before 3.2.17, 4.0 before 4.0.9, and 4.1 before 4.1.6, the parsed values of Accept-Language headers are cached in order to avoid repetitive parsing.
- 44%CVE-2021-35042Critical
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.
- 41%CVE-2021-23336Medium
The package python/cpython from 0 and before 3.6.13, from 3.7.0 and before 3.7.10, from 3.8.0 and before 3.8.8, from 3.9.0 and before 3.9.2 are vulnerable to Web Cache Poisoning via urllib.parse.parse_qsl and...
All Djangoproject products we track.
4 products, most vulnerabilities first. Find the ones you run, then open a product to see its versions and exploited flaws.
Running Djangoproject? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
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.
- Matched to
- Django on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
Our catalogue lists 126 published vulnerabilities across 4 products and 440 versions from Djangoproject.
None of Djangoproject's vulnerabilities is on the list of flaws known to be exploited today.
Django, with 123 published vulnerabilities. Its own page lists the ones known to be exploited.
Create a Precursor Intelligence account and track the Djangoproject products you run. We match them against every published flaw, give each one a risk score from 0 to 100 and tell you as soon as we spot one that affects you, by email, in the app or by webhook.