CVE-2026-71238
DjangoCRM: Hardcoded Django SECRET_KEY Enables Session and CSRF Token Forgery
CVSS Score
9.1
EPSS Score
0.0%
EPSS Percentile
0th
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. The repository also ships with DEBUG=True as the default, causing error pages to leak database credentials, email credentials, OAuth data, and internal file paths.
| CWE | CWE-798 |
| Vendor | djangocrm |
| Product | django-crm |
| Published | Aug 5, 2026 |
| Last Updated | Aug 5, 2026 |
Stay Ahead of the Next One
Get instant alerts for djangocrm django-crm
Be the first to know when new critical vulnerabilities affecting djangocrm django-crm are published — delivered to Slack, Telegram or Discord.
Get Free Alerts →
Free · No credit card · 60 sec setup
CVSS v3 Breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N Attack Vector
Attack Complexity
Privileges Required
User Interaction
Scope
Confidentiality
Integrity
Availability
Affected Versions
DjangoCRM / django-crm
0
Credits
Mirdavlatov Mira'zam