Django: 1.3.7 → 1.11.29
Django · upgrade impact · Official site ↗
Fixed by upgrading to 1.11.29 iVulnerabilities that affect 1.3.7 but no longer affect 1.11.29 — the security gain from this upgrade, by exploited status then exploitation probability.
Exploited first, then by exploitation probability (EPSS).
CVE-2019-19844 CRITICAL EPSS 35% ✓ cleared in 1.11.29 CVE-2015-0219 MEDIUM EPSS 7% ✓ cleared in 1.11.29 CVE-2016-7401 HIGH EPSS 6% ✓ cleared in 1.11.29 CVE-2014-0472 MEDIUM EPSS 6% ✓ cleared in 1.11.29 CVE-2016-6186 MEDIUM EPSS 6% ✓ cleared in 1.11.29 CVE-2015-2317 MEDIUM EPSS 5% ✓ cleared in 1.11.29 CVE-2014-0474 HIGH EPSS 5% ✓ cleared in 1.11.29 CVE-2015-0221 MEDIUM EPSS 4% ✓ cleared in 1.11.29 CVE-2015-8213 MEDIUM EPSS 4% ✓ cleared in 1.11.29 CVE-2015-5144 MEDIUM EPSS 4% ✓ cleared in 1.11.29 CVE-2015-0220 MEDIUM EPSS 3% ✓ cleared in 1.11.29 CVE-2015-0222 MEDIUM EPSS 3% ✓ cleared in 1.11.29 CVE-2014-0481 MEDIUM EPSS 2% ✓ cleared in 1.11.29 CVE-2014-0480 MEDIUM EPSS 2% ✓ cleared in 1.11.29 CVE-2015-2241 MEDIUM EPSS 2% ✓ cleared in 1.11.29 CVE-2014-0483 LOW EPSS 2% ✓ cleared in 1.11.29 CVE-2014-0473 MEDIUM EPSS 2% ✓ cleared in 1.11.29 CVE-2014-0482 MEDIUM EPSS 2% ✓ cleared in 1.11.29Still open in 1.11.29 iKnown vulnerabilities that affect 1.11.29 too — upgrading to it does not clear these.
These affect 1.11.29 as well — a later release may be needed.
CVE-2021-33203 MEDIUM EPSS 3% → fixed in 3.2.4