Threats Tagged 'cve-2026-71238'
View all threats tagged with 'cve-2026-71238'. Filter and sort to focus on specific types of threats.
Stop chasing alerts. Route them.
Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.
Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)
API access activates after upgrading in Console -> Billing.
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.
Filter Threats
Narrow down the results by type, severity, or affected countries
Threats Tagged 'cve-2026-71238'
Click on any threat for detailed analysis and mitigation recommendations
CVE-2026-71238: CWE-798 Use of Hard-coded Credentials in DjangoCRM django-crmCVE-2026-71238 0 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. Join the discussion | CVE Database V5 | 08/05/2026, 10:56:33 UTC Added: 08/05/2026, 11:12:01 UTC |
Showing 1 to 1 of 1 result