High severityPythonHardcoded SecretsHIGH confidence
Django Secret Key Literal
Django SECRET_KEY is hardcoded as a string literal (CWE-798).
Standards mapping
- OWASP ASVS
- V6.4.1 (L2)
Vulnerable vs. safe
Flagged by this check
SECRET_KEY = "django-insecure-abc123def456ghi789"Passes - the safe pattern
SECRET_KEY = os.environ["DJANGO_SECRET_KEY"]Why it matters & how to fix it
Django SECRET_KEY is hardcoded as a string literal (CWE-798). This key signs sessions, password-reset tokens, and CSRF tokens; committing it enables forgery. Read it from the environment (SECRET_KEY = os.environ["DJANGO_SECRET_KEY"]) and rotate the exposed key.
References
Rule ID integsec-python-django-secret-key-literal - engine: Opengrep - license: MIT - Copyright (c) IntegSec Inc.
TurboPentest runs this check automatically
Connect a GitHub repo and this check runs on every white-box pentest - AI-validated and reported with proof, from $99 per target.
Start a pentestRelated checks
- JavaScript / TypeScript - Hardcoded SecretsBasic Auth Credentials In URL
- JavaScript / TypeScript - Hardcoded SecretsDB Connection String With Credentials
- JavaScript / TypeScript - Hardcoded SecretsHardcoded Credential String
- JavaScript / TypeScript - Hardcoded SecretsHardcoded Crypto Key Or IV
- Python - Hardcoded SecretsBasic Auth Credentials In URL
- Python - Hardcoded SecretsDB Connection String Credentials