DjangoCRM - Hardcoded Django SECRET_KEY Enables Session and CSRF Token Forgery
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · High · None
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-798.
Summary
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2026-71238
- 2026-10-03 Alias added: GHSA-qc6p-hvpv-4f8h
References
Advisory 1
More DjangoCRM vulnerabilities
- TI-2026-49910 DjangoCRM - Server-Side Template Injection in Mass Mail Message Rendering CVSS 3.1HIGH 8.1
- TI-2026-61709 DjangoCRM django-crm Bulk Case Update bulk_views.py BulkUpdateCasesView authorization CVSS 4.0MEDIUM 5.3
- TI-2026-49911 DjangoCRM - Unauthenticated Open Redirect via toggle_default_sorting next_url Parameter CVSS 3.1MEDIUM 4.3
Sources
- CVE-2026-71238 · CVE Program
- CVE-2026-71238 · NVD
- FIRST EPSS
- GHSA-qc6p-hvpv-4f8h · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences