CVE-2026-71238: critical vulnerability in DjangoCRM django-crm
DjangoCRM - Hardcoded Django SECRET_KEY Enables Session and CSRF Token Forgery
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
28Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 9.1epss 0.4%
DjangoCRM ships with its Django SECRET_KEY hardcoded directly in the committed webcrm/settings.py rather than read from an environment variable. Since this key is used for session signing, CSRF token generation, and password reset tokens, anyone who reads the public repository can forge valid session cookies (including for the superadmin account), forge CSRF tokens, and forge password reset tokens, achieving full account takeover.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Affected products
DjangoCRM · django-crmRelated CVEs — DjangoCRM django-crm
In the same product, most dangerous first.
CVE-2026-71239HIGHDjangoCRM - Server-Side Template Injection in Mass Mail Message RenderingEPSS 0.4%CVE-2026-90806MEDIUMDjangoCRM django-crm Bulk Case Update bulk_views.py BulkUpdateCasesView authorizationEPSS 0.4%CVE-2026-71240MEDIUMDjangoCRM - Unauthenticated Open Redirect via toggle_default_sorting next_url ParameterEPSS 0.3%
References
https://github.com/DjangoCRM/django-crm