How to fix: Sensitive Endpoints Referenced in Page Source
References to potentially sensitive endpoints in the page source.
Why it matters
References to admin panels, debug endpoints help attackers map your attack surface.
Even if endpoints are protected, exposing their paths gives attackers specific targets.
How to fix it
- 1Remove references to internal/admin endpoints from client-side code.
- 2Use server-side rendering for admin navigation.
- 3Move API documentation behind authentication.
Code examples
Conditional render
{session?.isAdmin && <Link href="/admin">Admin Panel</Link>}References
Detected automatically by VulnRadar. The check id is sensitive-endpoints, 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 Sensitive Endpoints Referenced in Page Source?
- VulnRadar rates this low 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 sensitive-endpoints, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Sensitive Endpoints Referenced in Page Source map to?
- It maps to CWE-200. 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.