How to fix: Application Error Messages Exposed to Users
Detailed error messages visible in the page HTML.
Why it matters
Detailed errors reveal file paths, database types, library versions.
Verbose error messages reveal the technology stack and internal structure.
How to fix it
- 1Configure production to display generic error pages.
- 2Log detailed errors server-side only.
- 3Implement custom error handlers.
Code examples
Next.js error handling
'use client'
export default function Error() {
return <div><h1>Something went wrong</h1><p>Please try again later.</p></div>;
}References
Detected automatically by VulnRadar. The check id is verbose-error-messages, 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 Application Error Messages Exposed to Users?
- 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 verbose-error-messages, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Application Error Messages Exposed to Users 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.