CVE-2026-71238 DjangoCRM - Hardcoded Django SECRET_KEY Enables Session and CSRF Token Forgery
Hardcoded Django SECRET_KEY allows attackers to forge session cookies and CSRF tokens, leading to full account takeover.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-71238?
CVE-2026-71238 is a critical vulnerability in DjangoCRM django-crm, published on 5 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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.
Weakness: CWE-798
Which versions are affected by CVE-2026-71238?
How do I fix CVE-2026-71238?
No fix has been published for CVE-2026-71238 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-71238 being exploited?
There is no known exploitation of CVE-2026-71238 in the wild and no public exploit code.
Sources
Also known as GHSA-qc6p-hvpv-4f8h.