How severe is CVE-2020-24584?

CVE-2020-24584 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.

Is CVE-2020-24584 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 3% (87th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2020-24584?

CVE-2020-24584 primarily affects Djangoproject Django. In total, 6 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2020-24584?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2020-24584 published?

CVE-2020-24584 was published on 2020-09-01 and last updated on 2026-06-17.

CVE-2020-24584

CVE-2020-24584 is a high-severity vulnerability in Djangoproject Django with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-276.

Key facts

Severity: High (CVSS 3.x base score 7.5)
CVSS v2: 5.0
EPSS exploit prediction: 3% (87th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-276
Affected product: Djangoproject Django
Published: 2020-09-01
Last modified: 2026-06-17

Description

An issue was discovered in Django 2.2 before 2.2.16, 3.0 before 3.0.10, and 3.1 before 3.1.1 (when Python 3.7+ is used). The intermediate-level directories of the filesystem cache had the system's standard umask rather than 0o077.

Frequently asked questions

What is CVE-2020-24584?: An issue was discovered in Django 2.2 before 2.2.16, 3.0 before 3.0.10, and 3.1 before 3.1.1 (when Python 3.7+ is used). The intermediate-level directories of the filesystem cache had the system's standard umask rather than 0o077.
How severe is CVE-2020-24584?: CVE-2020-24584 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2020-24584 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 3% (87th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2020-24584?: CVE-2020-24584 primarily affects Djangoproject Django. In total, 6 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2020-24584?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2020-24584 published?: CVE-2020-24584 was published on 2020-09-01 and last updated on 2026-06-17.

References

Affected products (6)

cpe:2.3:a:djangoproject:django:*:*:*:*:*:*:*:*
cpe:2.3:o:canonical:ubuntu_linux:20.04:*:*:*:lts:*:*:*
cpe:2.3:o:fedoraproject:fedora:31:*:*:*:*:*:*:*
cpe:2.3:o:fedoraproject:fedora:32:*:*:*:*:*:*:*
cpe:2.3:o:fedoraproject:fedora:33:*:*:*:*:*:*:*
cpe:2.3:a:oracle:zfs_storage_appliance_kit:8.8:*:*:*:*:*:*:*

More vulnerabilities in Djangoproject Django

CVE-2014-0474 — Critical (CVSS 10.0): The (1) FilePathField, (2) GenericIPAddressField, and (3) IPAddressField model field classes in Django before 1.4.11,…
CVE-2026-4277 — Critical (CVSS 9.8): An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. Add permissions on inline model…
CVE-2024-53908 — Critical (CVSS 9.8): An issue was discovered in Django 5.1 before 5.1.4, 5.0 before 5.0.10, and 4.2 before 4.2.17. Direct usage of the…
CVE-2023-31047 — Critical (CVSS 9.8): In Django 3.2 before 3.2.19, 4.x before 4.1.9, and 4.2 before 4.2.1, it was possible to bypass validation when using…
CVE-2022-34265 — Critical (CVSS 9.8): 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…
CVE-2022-28347 — Critical (CVSS 9.8): 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…

All CVEs affecting Djangoproject Django →

Other CWE-276 (Incorrect Default Permissions) vulnerabilities

CVE-2022-42150 — Critical (CVSS 10.0): TinyLab linux-lab v1.1-rc1 and cloud-labv0.8-rc2, v1.1-rc1 are vulnerable to insecure permissions. The default…
CVE-2020-29492 — Critical (CVSS 10.0): Dell Wyse ThinOS 8.6 and prior versions contain an insecure default configuration vulnerability. A remote…
CVE-2020-29491 — Critical (CVSS 10.0): Dell Wyse ThinOS 8.6 and prior versions contain an insecure default configuration vulnerability. A remote…
CVE-2025-40585 — Critical (CVSS 9.9): A vulnerability has been identified in Energy Services (All versions with G5DFR). Affected solutions using G5DFR…
CVE-2019-19896 — Critical (CVSS 9.9): In IXP EasyInstall 6.2.13723, there is Remote Code Execution via weak permissions on the Engine Service share. The…
CVE-2020-37129 — Critical (CVSS 9.8): Memu Play 7.1.3 contains an insecure folder permissions vulnerability that allows low-privileged users to modify the…

Browse all CWE-276 (Incorrect Default Permissions) vulnerabilities →