How to fix: Debug header present in production response
A debug-related response header is present (e.g., X-Debug-Info, X-Debug-Token, X-Symfony-Debug), revealing application internals.
Why it matters
Debug headers expose internal application state, configuration, database query counts, or profiler data, information that helps attackers understand the application and identify inefficiencies to target.
Debug headers must not be present in production responses.
How to fix it
- 1Disable debug mode in production
- 2Audit your framework config to ensure debug output is suppressed
- 3Symfony: remove the Debug toolbar; Laravel: set APP_DEBUG=false
Code examples
Strip debug headers in Nginx
proxy_hide_header X-Debug-Token;
proxy_hide_header X-Debug-Token-Link;
proxy_hide_header X-Debug-Info;References
Detected automatically by VulnRadar. The check id is x-debug-header-exposed, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is Debug header present in production response?
- VulnRadar rates this medium severity in the headers 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 x-debug-header-exposed, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Debug header present in production response 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.