CVE-2019-19844: Potential account hijack via password reset form in Django
Summary
CVE-2019-19844: Django Potential account hijack via password reset form. Affects django across 3 version ranges.
< 1.11.27
>= 2.0, < 2.2.9
>= 3.0, < 3.0.1
Fixed in 1.11.27, 2.2.9 or 3.0.1, depending on the release line you run. How to fix ↓
Also tracked for
- py-django · Alpine:v3.10
The same CVE-2019-19844 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Django is a popular Python web framework that provides a set of tools and libraries for building web applications. It includes features for user authentication and password management. However, versions of Django before 1.11.27, 2.x before 2.2.9, and 3.x before 3.0.1 are vulnerable to a potential account hijack via the password reset form.
Vulnerability Detail
The vulnerability arises from a flaw in the password reset functionality of Django. An attacker can exploit this vulnerability by crafting an email address that matches an existing user's email address after case transformation of Unicode characters. This allows the attacker to receive a password reset token for the targeted user account. The impact of this vulnerability is significant as it enables unauthorized access to user accounts, potentially leading to data breaches and unauthorized actions on behalf of the user.
How To Fix
Latest published version: 6.1.2 as of 22 Oct 2026
pip install --upgrade "django==6.1.2"
Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.
If you can't move to the latest
The minimum fixed version depends on the release line you run.
-
< 1.11.271.11.27pip install --upgrade "django==1.11.27" -
>= 2.0, < 2.2.92.2.9pip install --upgrade "django==2.2.9" -
>= 3.0, < 3.0.13.0.1pip install --upgrade "django==3.0.1"
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
There is no specific workaround mentioned for this vulnerability.
Conclusion
In conclusion, the vulnerability in Django's password reset form can lead to account hijacking and unauthorized access to user accounts. It is crucial to upgrade to the latest patched versions of Django to mitigate this issue. For further support on vulnerability remediation, you can contact DevNack.com.
See every vulnerability recorded for django →
FAQ
The impact of this vulnerability is significant as it allows unauthorized access to user accounts, potentially leading to data breaches and unauthorized actions on behalf of the user.
You can use Vulert's playground (https://vulert.com/scanner) to check if your Django version is affected by this vulnerability. Simply upload your Pipfile.lock and it will provide real-time alerts for open-source vulnerabilities.
There are no known exploits available for this vulnerability at the moment.
Yes, the CVSS score for this vulnerability is 9.8, indicating a critical severity level.
For more information about this vulnerability, you can refer to the GitHub advisory database: https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2020/01/GHSA-vfq6-hq5r-27r6/GHSA-vfq6-hq5r-27r6.json
References
Related vulnerabilities
Recent vulnerabilities recorded for django.