CVE-2026-71238 — DjangoCRM ships with its Django SECRET_KEY hardcoded directly in the committed…¶
Key facts
CVE-2026-71238 is a Critical (9.1) vulnerability: DjangoCRM ships with its Django SECRET_KEY hardcoded directly in the committed…. This entry ships a detection-only PoC and a Docker test lab.
| CVE | CVE-2026-71238 |
| Severity | Critical (9.1) |
| Detection / prevention | — |
| PoC | poc.py |
| Source | 2026/CVE-2026-71238/ |
Details¶
English | 한국어
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. 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.
Vulnerability Details¶
| Property | Value |
|---|---|
| CVE ID | CVE-2026-71238 |
| Type | XSS |
| CVSS Score | 9.1 |
Proof of Concept¶
Download¶
# Download PoC script
curl -O https://raw.githubusercontent.com/fankh/vulnerability-poc/main/2026/CVE-2026-71238/poc.py
Usage¶
# Run PoC against target
python3 poc.py --target <TARGET_URL>
# With authentication
python3 poc.py --target <TARGET_URL> --username <USER> --password <PASS>
⚠️ Warning: This PoC is for authorized security testing only. It uses detection-only techniques and does not exploit or damage target systems.
Test Lab¶
This repository includes a Docker-based test environment with both vulnerable and patched applications.
Quick Start¶
# Clone and navigate to CVE directory
cd CVE-2026-71238
# Start both applications
docker-compose up -d
# Run tests
./run-tests.sh # Linux/Mac
./run-tests.ps1 # Windows PowerShell
Application Endpoints¶
| Application | URL | Status |
|---|---|---|
| Vulnerable App | http://localhost:8080 | Shows vulnerability |
| Patched App | http://localhost:8081 | Demonstrates fix |
Directory Structure¶
├── README.md # English documentation
├── README_KO.md # Korean documentation
├── poc.py # PoC detection script
├── docker-compose.yml # Container orchestration
├── run-tests.sh # Linux/Mac test runner
├── run-tests.ps1 # Windows test runner
├── vulnerable-app/ # Vulnerable version
│ ├── app.py
│ ├── Dockerfile
│ └── requirements.txt
└── patched-app/ # Fixed version
├── app.py
├── Dockerfile
└── requirements.txt
References¶
- https://github.com/DjangoCRM/django-crm
Generated by PoC Generator on 2026-08-10T00:50:29.990659113
Frequently asked questions¶
What is CVE-2026-71238?¶
CVE-2026-71238 is a Critical (9.1) vulnerability: DjangoCRM ships with its Django SECRET_KEY hardcoded directly in the committed…. This entry ships a detection-only PoC and a Docker test lab.
How do I detect CVE-2026-71238?¶
Run the detection-only PoC included with this entry against your Docker test lab to confirm whether a target is affected; pair it with your own IDS logging.
How do I block or mitigate CVE-2026-71238?¶
Upgrade to a fixed version per the vendor advisory; the NVD record lists the affected versions. Use the included PoC to verify your remediation.
For authorized security testing and research only. See the full source and NVD record.