How to fix: Debug Toolbar Active on Public Page
Django Debug Toolbar or Laravel Debugbar/PHP Debug Bar static assets were found referenced in a publicly reachable page.
Why it matters
These toolbars render executed SQL queries, request/session data, environment variables, and internal timing information directly in the page for anyone who loads it.
Debug toolbars are development conveniences that should never load outside a local/staging environment restricted to trusted developers. Their presence on any publicly reachable page means the application is running with debug mode enabled in production.
How to fix it
- 1Disable the debug toolbar in production configuration (DEBUG=False for Django; APP_DEBUG=false and remove the debugbar package for Laravel).
- 2Gate any debug tooling behind an environment check that cannot be overridden by a request parameter.
- 3Confirm no debug middleware is registered when the app is deployed.
Code examples
Django settings.py
DEBUG = False
INSTALLED_APPS = [a for a in INSTALLED_APPS if a != 'debug_toolbar']References
Detected automatically by VulnRadar. The check id is debug-toolbar-assets-exposed, stable across every scan so you can filter or diff on it.
More config checks
- MediumNo Rate-Limit Policy Detected
- MediumVary: Cookie Missing on Cookie-Bearing Response
- LowSet-Cookie Header Exceeds 4 KB
- LowVary Header Missing on Compressed Responses
- InfoDownloadable Content Served as inline
- InfoX-XSS-Protection Header Is Deprecated
- LowServer-Timing Exposes Cache Timings
- LowVary: Cookie on Static Resource
Questions
- How severe is Debug Toolbar Active on Public Page?
- VulnRadar rates this high severity in the config 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 debug-toolbar-assets-exposed, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Debug Toolbar Active on Public Page 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.