ChainPyPI:Django
Django: related fixes (2021–2022)
3 CVEs over 3 generations, 2 Jul 2021 to 12 Apr 2022.
Family tree
Left to right by publication date.Oldest first. Select a CVE to open it.- CVE-2021-350422 Jul 2021 First in the chain
- CVE-2022-2834612 Apr 2022 related to CVE-2021-35042
- CVE-2022-2834712 Apr 2022 related to CVE-2021-35042related to CVE-2022-28346
Exploited in the wild (CISA KEV) Not in KEV Priority score (0 to 100) High confidence Medium Low Link confidenceHow strong the evidence is that two CVEs are related. High: stated in the CVE text or linked in an advisory, or the same code was patched one release apart. Medium: the same code, or a version step plus a similar description. Low: similar description only.
CVEs in this family
Table view of the tree| CVE | Published | Title | Linked from | Priority |
|---|---|---|---|---|
| CVE-2021-35042 | 2 Jul 2021 | 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… · fixed in 3.2.5 | First in chain | 24.8 |
| CVE-2022-28346 | 12 Apr 2022 | 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 · fixed in 4.0.4 | CVE-2021-35042 · related · Medium | 24.5 |
| CVE-2022-28347 | 12 Apr 2022 | A SQL injection issue was discovered in QuerySet.explain() in Django 2.2 before 2.2.28, 3.2 before 3.2.13, and 4.0… · fixed in 4.0.4 | CVE-2021-35042 · related · Medium | 17.4 |