ChainPyPI:Django
Django: related fixes (2010–2013)
3 CVEs over 2 generations, 14 Sep 2010 to 16 Sep 2013.
Family tree
Left to right by publication date.Oldest first. Select a CVE to open it.- CVE-2010-308214 Sep 2010 First in the chain
- CVE-2011-069614 Feb 2011 related to CVE-2010-3082
- CVE-2013-431516 Sep 2013 related to CVE-2010-3082
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-2010-3082 | 14 Sep 2010 | Cross-site scripting (XSS) vulnerability in Django 1.2.x before 1.2.2 allows remote attackers to inject arbitrary web… · fixed in 1.2.2 | First in chain | 16.0 |
| CVE-2011-0696 | 14 Feb 2011 | Django 1.1.x before 1.1.4 and 1.2.x before 1.2.5 does not properly validate HTTP requests that contain an… · fixed in 1.2.5 | CVE-2010-3082 · related · Medium | 15.2 |
| CVE-2013-4315 | 16 Sep 2013 | Directory traversal vulnerability in Django 1.4.x before 1.4.7, 1.5.x before 1.5.3, and 1.6.x before 1.6 beta 3 allows… · fixed in 1.5.3 | CVE-2010-3082 · related · Medium | 17.6 |