How to fix: Django debug page exposing settings and installed apps
Django's DEBUG = True is enabled in production, exposing detailed error pages with source code, local variables, and settings.
Why it matters
Django debug pages expose full source code at the error location, all local variables at every stack frame, all installed apps and middleware, and Django settings (including SECRET_KEY if it appears in a traceback), a critical information disclosure.
DEBUG = True is appropriate only in development. Production deployments must have DEBUG = False.
How to fix it
- 1Set DEBUG = False in production settings
- 2Set ALLOWED_HOSTS to your actual domain names
- 3Configure a proper error logging backend (Sentry, logging module)
Code examples
Disable DEBUG mode in production
# settings.py: never set DEBUG=True in production
DEBUG = os.environ.get('DJANGO_DEBUG', 'False') == 'True'
# ALLOWED_HOSTS must be set when DEBUG=False
ALLOWED_HOSTS = os.environ.get('ALLOWED_HOSTS', '').split(',')References
Detected automatically by VulnRadar. The check id is django-debug-page, stable across every scan so you can filter or diff on it.
More content checks
- MediumPotential Open Redirect Parameters
- HighDirectory Listing Appears Enabled
- MediumSensitive File References Detected
- HighPotentially Outdated JavaScript Libraries
- Inforobots.txt Present - Review Manually
- InfoCMS / Technology Fingerprinting
- MediumPotentially Dangerous Inline JavaScript
- LowServer version disclosed in response header
Questions
- How severe is Django debug page exposing settings and installed apps?
- VulnRadar rates this critical severity in the content category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id django-debug-page, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Django debug page exposing settings and installed apps map to?
- It maps to CWE-489. In the OWASP Top 10 it falls under A05:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.