Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

DjangoCRM - Hardcoded Django SECRET_KEY Enables Session and CSRF Token Forgery

CVSS 3.1 9.1 CRITICALCheck source for fixed versionsKEV status unknown

Historical advisory recorded 23 Oct 2026 15:48:27 UTC. Read the latest advisory.

cve-program · CVE-2026-71238

Published

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.

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2026-71238

Published

django-crm

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "DjangoCRM",
                    "product": "django-crm",
                    "programFiles": [
                        "webcrm/settings.py"
                    ],
                    "versions": [
                        {
                            "version": "0",
                            "status": "affected"
                        }
                    ],
                    "defaultStatus": "unknown"
                }

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 22 Nov 14:25 UTC · 274 of 275 readable · 270 fully read · documentation 469/469 current