CVE-2019-19844

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 34.8%, top 2% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Weaponized
9.8EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 54%
  • Public exploit code is available (Exploit-DB (verified), epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 54%CVSS: 9.8Exploit: Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed: 0

A fix is available — apply it.

Django before 1.11.27, 2.x before 2.2.9, and 3.x before 3.0.1 allows account takeover. A suitably crafted email address (that is equal to an existing user's email address after case transformation of Unicode characters) would allow an attacker to be sent a password reset token for the matched user account. (One mitigation in the new releases is to send password reset tokens only to the registered user email address.)

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
75(Track*)
EG Risk 75/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation65% × 40%
Automatability30% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
54%
EPSS %ILE
99%
KEV
Not listed

Published

December 18, 2019

Last Modified

November 21, 2024

Advisory Details (9)

Auto-updated Sep 6, 2026
No patch confirmed yet.
generic

Django security releases issued: 3.0.1, 2.2.9, and 1.11.27 | Weblog | Django

https://www.djangoproject.com/weblog/2019/dec/18/security-releases/
generic

[SECURITY] [DSA 4598-1] python-django security update

https://www.debian.org/security/2020/dsa-4598
generic

NetApp Product Security

https://security.netapp.com/advisory/ntap-20200110-0003/
generic

Django: Multiple vulnerabilities (GLSA 202004-17) — Gentoo security

https://security.gentoo.org/glsa/202004-17
generic

Bugtraq: [SECURITY] [DSA 4598-1] python-django security update

https://seclists.org/bugtraq/2020/Jan/9
generic

[SECURITY] Fedora 31 Update: python-django-2.2.9-1.fc31 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/HCM2DPUI7TOZWN4A6JFQFUVQ2XGE7GUD/
generic

Redirecting to Google Groups

https://groups.google.com/forum/#%21topic/django-announce/3oaB2rVH3a0
generic

Archive of security issues | Django documentation | Django

https://docs.djangoproject.com/en/dev/releases/security/
generic

Packet Storm Security

http://packetstormsecurity.com/files/155872/Django-Account-Hijack.html

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupython3-django (1:1.11.20-1ubuntu0.3) @ disco2026-05-27ubuntu
ubuntupython-django-doc (1.6.11-0ubuntu1.3+esm7) @ trusty2026-05-27ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(13 across 13 ecosystems)
Alpine:v3.10(1)
PackageVulnerable rangeFixed inDependents
py-django1.10.5-r0 ... 1.8.8-r0 (40 versions)1.11.27-r0—
Alpine:v3.11(1)
PackageVulnerable rangeFixed inDependents
py3-django1.10.5-r0 ... 1.8.8-r0 (42 versions)1.11.27-r0—
Alpine:v3.12(1)
PackageVulnerable rangeFixed inDependents
py3-django1.10.5-r0 ... 1.8.8-r0 (42 versions)1.11.27-r0—
Alpine:v3.8(1)
PackageVulnerable rangeFixed inDependents
py-django1.10.5-r0 ... 1.8.8-r0 (39 versions)1.11.27-r0—
Alpine:v3.9(1)
PackageVulnerable rangeFixed inDependents
py-django1.10.5-r0 ... 1.8.8-r0 (39 versions)1.11.27-r0—
Debian:10(1)
PackageVulnerable rangeFixed inDependents
python-django1:1.11.21-1, 1:1.11.22-1, 1:1.11.22-1~deb10u1, 1:1.11.23-1~deb10u11:1.11.27-1~deb10u1—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
python-django—2:2.2.9-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
python-django—2:2.2.9-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
python-django—2:2.2.9-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
python-django—2:2.2.9-1—
Debian:8(1)
PackageVulnerable rangeFixed inDependents
python-django1.7.10-1 ... 1.7.9-1 (16 versions)1.7.11-1+deb8u8—
Debian:9(1)
PackageVulnerable rangeFixed inDependents
python-django1:1.10.7-2 ... 1:1.10.7-2+deb9u6 (7 versions)1:1.10.7-2+deb9u7—
PyPI(1)
PackageVulnerable rangeFixed inDependents
django1.0.1 ... 2.2.8 (177 versions)2.2.9—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(2)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 6× in last 7d / 21× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 119 total refreshes for this CVE.

  1. 2026-09-07 22:51 UTCOSV refresh
  2. 2026-09-07 15:57 UTCEPSS rescore
  3. 2026-09-06 13:44 UTCEPSS rescore
  4. 2026-09-05 15:24 UTCEPSS rescore
  5. 2026-09-04 13:56 UTCEPSS rescore
  6. 2026-09-02 14:07 UTCEPSS rescore
  7. 2026-08-30 19:13 UTCEPSS rescore
  8. 2026-08-30 01:18 UTCEPSS rescore
  9. 2026-08-28 21:36 UTCEPSS rescore
  10. 2026-08-26 14:42 UTCEPSS rescore
  11. 2026-08-25 13:45 UTCEPSS rescore
  12. 2026-08-24 14:11 UTCEPSS rescore
  13. 2026-08-21 23:45 UTCEPSS rescore
  14. 2026-08-21 08:14 UTCOSV refresh
  15. 2026-08-20 22:51 UTCEPSS rescore
  16. 2026-08-19 17:00 UTCEPSS rescore
  17. 2026-08-18 13:44 UTCEPSS rescore
  18. 2026-08-16 14:52 UTCEPSS rescore
  19. 2026-08-16 02:10 UTCEPSS rescore
  20. 2026-08-15 01:26 UTCEPSS rescore
  21. 2026-08-12 13:47 UTCEPSS rescore
  22. 2026-08-07 16:23 UTCEPSS rescore
  23. 2026-08-06 13:43 UTCEPSS rescore
  24. 2026-08-05 21:51 UTCOSV refresh
  25. 2026-08-05 19:13 UTCEPSS rescore
Show 75 more
  1. 2026-08-04 15:05 UTCEPSS rescore
  2. 2026-08-02 02:23 UTCEPSS rescore
  3. 2026-08-01 04:12 UTCEPSS rescore
  4. 2026-07-30 16:24 UTCEPSS rescore
  5. 2026-07-30 01:27 UTCEPSS rescore
  6. 2026-07-28 15:32 UTCEPSS rescore
  7. 2026-07-26 14:51 UTCEPSS rescore
  8. 2026-07-25 14:14 UTCEPSS rescore
  9. 2026-07-24 14:14 UTCEPSS rescore
  10. 2026-07-24 14:14 UTCEPSS rescore
  11. 2026-07-23 14:15 UTCEPSS rescore
  12. 2026-07-23 01:43 UTCEG score recompute
  13. 2026-07-22 22:23 UTCEG score recompute
  14. 2026-07-22 14:05 UTCEPSS rescore
  15. 2026-07-21 15:22 UTCEPSS rescore
  16. 2026-07-21 15:22 UTCEPSS rescore
  17. 2026-07-20 17:04 UTCEPSS rescore
  18. 2026-07-20 17:04 UTCEPSS rescore
  19. 2026-07-19 23:38 UTCOSV refresh
  20. 2026-07-19 14:28 UTCEPSS rescore
  21. 2026-07-19 14:28 UTCEPSS rescore
  22. 2026-07-18 10:01 UTCEPSS rescore
  23. 2026-07-16 16:59 UTCEPSS rescore
  24. 2026-07-16 16:59 UTCEPSS rescore
  25. 2026-07-15 16:55 UTCEPSS rescore
  26. 2026-07-15 16:55 UTCEPSS rescore
  27. 2026-07-13 06:10 UTCEPSS rescore
  28. 2026-07-13 06:10 UTCEPSS rescore
  29. 2026-07-12 05:43 UTCEPSS rescore
  30. 2026-07-12 05:43 UTCEPSS rescore
  31. 2026-07-11 08:24 UTCEPSS rescore
  32. 2026-07-11 08:24 UTCEPSS rescore
  33. 2026-07-09 19:06 UTCEPSS rescore
  34. 2026-07-08 15:11 UTCEPSS rescore
  35. 2026-07-07 13:43 UTCEPSS rescore
  36. 2026-07-05 02:27 UTCEPSS rescore
  37. 2026-07-02 14:01 UTCOSV refresh
  38. 2026-07-01 15:03 UTCEPSS rescore
  39. 2026-07-01 15:03 UTCEPSS rescore
  40. 2026-06-30 23:20 UTCEPSS rescore
  41. 2026-06-29 14:03 UTCEPSS rescore
  42. 2026-06-28 04:54 UTCEPSS rescore
  43. 2026-06-28 04:54 UTCEPSS rescore
  44. 2026-06-27 03:06 UTCEPSS rescore
  45. 2026-06-25 13:47 UTCEPSS rescore
  46. 2026-06-25 13:47 UTCEPSS rescore
  47. 2026-06-24 14:03 UTCEPSS rescore
  48. 2026-06-24 14:03 UTCEPSS rescore
  49. 2026-06-23 21:31 UTCEPSS rescore
  50. 2026-06-23 21:30 UTCEPSS rescore
  51. 2026-06-22 14:23 UTCEPSS rescore
  52. 2026-06-21 01:57 UTCEPSS rescore
  53. 2026-06-21 01:57 UTCEPSS rescore
  54. 2026-06-19 19:23 UTCEPSS rescore
  55. 2026-06-19 19:23 UTCEPSS rescore
  56. 2026-06-18 17:50 UTCEPSS rescore
  57. 2026-06-17 17:50 UTCEPSS rescore
  58. 2026-06-16 17:50 UTCEPSS rescore
  59. 2026-06-15 17:45 UTCEPSS rescore
  60. 2026-06-14 23:15 UTCEPSS rescore
  61. 2026-06-14 23:15 UTCEPSS rescore
  62. 2026-06-14 12:13 UTCOSV refresh
  63. 2026-06-13 22:58 UTCEPSS rescore
  64. 2026-06-12 23:09 UTCEPSS rescore
  65. 2026-06-11 13:58 UTCEPSS rescore
  66. 2026-06-10 22:16 UTCEPSS rescore
  67. 2026-06-10 13:19 UTCEPSS rescore
  68. 2026-06-08 14:15 UTCEPSS rescore
  69. 2026-06-07 15:23 UTCEPSS rescore
  70. 2026-06-07 15:23 UTCEPSS rescore
  71. 2026-06-06 13:45 UTCEPSS rescore
  72. 2026-06-06 13:45 UTCEPSS rescore
  73. 2026-06-05 22:45 UTCEPSS rescore
  74. 2026-06-05 22:45 UTCEPSS rescore
  75. 2026-06-04 13:10 UTCEPSS rescore

Publicly available exploits

(4 references)

Working exploit code is in the public domain (3 GitHub PoCs) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoC0xsha/CVE_2019_19844
    First seen Jan 18, 2020

    CVE-2019-19844 Docker Edition

    Open source ↗
  • GitHub PoCandripwn/django_cve201919844
    First seen Dec 25, 2019

    PoC for CVE-2019-19844 ( https://www.djangoproject.com/weblog/2019/dec/18/security-releases/ )

    Open source ↗
  • Exploit-DBEDB-47879✓ verified
    First seen Dec 24, 2019

    Django < 3.0 < 2.2 < 1.11 - Account Hijack

    Open source ↗
  • GitHub PoCryu22e/django_cve_2019_19844_poc
    First seen Dec 21, 2019

    PoC for CVE-2019-19844(https://www.djangoproject.com/weblog/2019/dec/18/security-releases/)

    Open source ↗

Frequently asked(5)

What is CVE-2019-19844?
CVE-2019-19844 is a critical vulnerability published on December 18, 2019. Django before 1.11.27, 2.x before 2.2.9, and 3.x before 3.0.1 allows account takeover. A suitably crafted email address (that is equal to an existing user's email address after case transformation of Unicode characters) would allow an attacker to be sent a password reset token for the matched user…
When was CVE-2019-19844 disclosed?
CVE-2019-19844 was first published in the National Vulnerability Database on December 18, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-19844 actively exploited?
CVE-2019-19844 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 54% probability of exploitation in the next 30 days, which ranks it in the top 1.1% of all scored CVEs.
What is the CVSS score of CVE-2019-19844?
CVE-2019-19844 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2019-19844?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-19844, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2019-19844

Explore →

Is Your Infrastructure Affected by CVE-2019-19844?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs