How to fix: Laravel debug mode enabled in production
Laravel's APP_DEBUG=true is enabled in production, showing detailed error pages with application code, stack traces, and environment variables.
Why it matters
Laravel debug mode exposes full stack traces, local variables, all configuration values (including database credentials if they appear in traces), and can allow code execution via the Ignition debug interface on older versions.
APP_DEBUG must be false in production environments.
How to fix it
- 1Set APP_DEBUG=false in .env for production
- 2Set APP_ENV=production
- 3Configure error logging to a server-side handler only
Code examples
Set APP_DEBUG=false in production
# .env (production)
APP_DEBUG=false
APP_ENV=production
# config/app.php
'debug' => env('APP_DEBUG', false),References
Detected automatically by VulnRadar. The check id is laravel-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 Laravel debug mode enabled in production?
- 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 laravel-debug-page, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Laravel debug mode enabled in production 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.