CVE-2021-3281Not scoredCWE-22

CVE-2021-3281: Djangoproject vulnerability

Djangoproject · Django

Vendor fix available · Affected: Djangoproject · Exploitation: possible (1 to 10%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

7.6%probability of exploitation in the next 30 days

94th percentile

050100

Higher than 94% of scored CVEs

Not scored yet. The CVE record carries no CVSS score.

DescriptionCVE.org

In Django 2.2 before 2.2.18, 3.0 before 3.0.12, and 3.1 before 3.1.6, the django.utils.archive.extract method (used by "startapp --template" and "startproject --template") allows directory traversal via an archive with absolute paths or relative paths with dot segments.

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Possible (1 to 10%). EPSS between 1% and 10%.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Path Traversal · File and Path Handling
Vendor: Djangoproject
Published: February 2021
Band: Possible (1 to 10%), February 2021
Bounty reports: 1 disclosed on HackerOne

Disclosed bug bounty reports about CVE-2021-3281

The reports on HackerOne that name this CVE, with HackerOne's own outcome. Titles and metadata only.

Path traversal via archive.extract - CVE 2021-3281 incomplete patchDjango · 2025 · low severityValid

CoverageNo articles yet

No CyberSIXT article names CVE-2021-3281 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.