ChainPyPI:Django
Django: related fixes (2011–2015)
3 CVEs over 2 generations, 19 Oct 2011 to 14 Jul 2015.
Family tree
Left to right by publication date.Oldest first. Select a CVE to open it.- CVE-2011-413719 Oct 2011 First in the chain
- CVE-2011-413819 Oct 2011 No direct link to an earlier CVE
- CVE-2015-514414 Jul 2015 related to CVE-2011-4137related to CVE-2011-4138
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-2011-4137 | 19 Oct 2011 | The verify_exists functionality in the URLField implementation in Django before 1.2.7 and 1.3.x before 1.3.1 relies on… | First in chain | 17.5 |
| CVE-2011-4138 | 19 Oct 2011 | The verify_exists functionality in the URLField implementation in Django before 1.2.7 and 1.3.x before 1.3.1… | First in chain | 16.8 |
| CVE-2015-5144 | 14 Jul 2015 | Django before 1.4.21, 1.5.x through 1.6.x, 1.7.x before 1.7.9, and 1.8.x before 1.8.3 uses an incorrect regular… · fixed in 1.8.3 | CVE-2011-4137 · related · Medium | 17.6 |