VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

django-registration: vulnerability history, versions and safety

django-registration is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 22 releases, first recorded in Apr 2021. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded L1 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all django-registration vulnerabilities

Vulert verdict on django-registration 5.2.1 i

Updated on 23 Oct 2026

Good news: 5.2.1, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 75/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Widely used
  • Community Quiet

What to do: Stay on 5.2.1 or newer. This can change: a vulnerability disclosed tomorrow can affect 5.2.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 5.2.1 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 06 Apr 2021 i
  • Highest CVSS 3.7 i
  • With no published fix 0 i
  • Depended on by 194 packages i
  • Stars 943 i
  • OpenSSF scorecard 3/10 i
  • Last release 18 months ago i
  • Licence BSD-3-Clause i

Version list, release dates, licence and dependants published by PyPI, refreshed 22 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for django-registration, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
5.2.1 07 Apr 2025 none BSD-3-Clause — Details →
5.2.0a0 07 Apr 2025 none BSD-3-Clause — Details →
5.1.0 08 Nov 2024 none BSD-3-Clause — Details →
3.4.0 04 Jul 2023 none BSD-3-Clause — Details →
3.3.0 28 May 2022 none BSD-3-Clause — Details →
3.2.0 21 Jun 2021 none BSD-3-Clause — Details →
3.1.2 01 Apr 2021 none non-standard — Details →
3.1.1 21 Sep 2020 L1 U1 non-standard Yes Details →
3.1.0 26 Jan 2020 L1 U1 non-standard Yes Details →
3.0.1 07 May 2019 L1 U1 non-standard Yes Details →
3.0.0 04 Sep 2018 L1 U1 non-standard Yes Details →
2.5.2 02 Sep 2018 L1 U1 non-standard Yes Details →
2.5.1 02 Sep 2018 L1 U1 non-standard Yes Details →
2.5.0 02 Sep 2018 L1 U1 non-standard Yes Details →
2.4.1 21 Jan 2018 L1 U1 non-standard Yes Details →
2.4.0 21 Jan 2018 L1 U1 non-standard Yes Details →
2.3.0 23 Sep 2017 L1 U1 non-standard Yes Details →
2.2.0 12 Nov 2016 L1 U1 non-standard Yes Details →
2.1.2 20 Jun 2016 L1 U1 non-standard Yes Details →
2.1.1 13 Jun 2016 L1 U1 non-standard Yes Details →
2.1.0 30 May 2016 L1 U1 non-standard Yes Details →
2.0.4 10 Jan 2016 L1 U1 non-standard Yes Details →
2.0.3 22 Nov 2015 L1 U1 non-standard Yes Details →
2.0.2 21 Nov 2015 L1 U1 non-standard Yes Details →
2.0.1 21 Nov 2015 L1 U1 non-standard Yes Details →
2.0.0 21 Nov 2015 L1 U1 non-standard Yes Details →
1.0.0 17 Jun 2013 L1 U1 non-standard Yes Details →
0.8.0 24 Mar 2012 L1 U1 non-standard Yes Details →
0.7.0 06 Nov 2008 L1 U1 non-standard Yes Details →

All 29 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 2 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for django-registration

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2021-21416: Potential sensitive information disclosure in django-registration 3.7 low 3.1.2 06 Apr 2021
CVE-2021-21416: django-registration - Sensitive Data Exposure in User Registration N/A unrated 3.1.2 01 Apr 2021

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About django-registration

Is django-registration safe to use?

Vulert records 2 vulnerabilities for django-registration in PyPI: 0 critical, 0 high, 0 medium and 1 low, plus 1 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is django-registration's Vulert package health score?

Vulert scores django-registration 75/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of django-registration affected?

No. 5.2.1, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of django-registration should I use?

5.2.1 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does django-registration have?

2 vulnerabilities are recorded for django-registration in the PyPI ecosystem: 0 critical, 0 high, 0 medium and 1 low, plus 1 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new django-registration vulnerabilities disclosed?

0 vulnerabilities were recorded for django-registration in the last 12 months, and the oldest entry in this database dates to 01 Apr 2021. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of django-registration are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor django-registration for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the django-registration version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.