How to fix: PHP error/warning in page content
A PHP error, warning, or notice is displayed in the page output, revealing file paths and internal application details.
Why it matters
PHP errors reveal absolute file paths (e.g., /var/www/html/app/...), PHP version, and internal application logic, helping attackers map the server filesystem and identify vulnerabilities.
PHP display_errors should be disabled in production; errors should be logged, not displayed.
How to fix it
- 1Set display_errors = Off in php.ini or .htaccess
- 2Set log_errors = On and log_errors to a server-side file
- 3Set error_reporting to E_ALL in development only
Code examples
Disable error display in PHP production config
// php.ini (production)
display_errors = Off
log_errors = On
error_log = /var/log/php/error.log
// Or in code:
ini_set('display_errors', '0');
error_reporting(E_ALL);
ini_set('log_errors', '1');References
Detected automatically by VulnRadar. The check id is php-error-in-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 PHP error/warning in page content?
- VulnRadar rates this medium 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 php-error-in-page, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does PHP error/warning in page content map to?
- It maps to CWE-209. 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.