- Public source or documentation names an internal route.
- An anonymous request receives the endpoint's genuine response rather than an access denial.
Internal Endpoint Exposure
An endpoint described or intended as internal is reachable from the public application boundary.
Follow only the disclosed route with a read-only anonymous request and confirm identity from minimal response markers.
Related entries
Connected case files
Margin Notes
Missing Authentication / Public Source Map Disclosure
Margin Notes exposed a source map containing the route and response handling for a hidden diagnostic endpoint. One anonymous Caido request returned build data, runtime details, and the lab flag.
Flap Copy
Public Metadata Disclosure / Internal Route Exposure
Flap Copy’s landing page disclosed its PWA manifest. Comparing it with the public AASA file revealed an unadvertised staff route, and one request returned internal handoff details plus the redacted flag.
Routing Slip
Missing Authentication / Sensitive Information Disclosure
Routing Slip’s developer portal linked the live OpenAPI file. Bearer authentication was required globally, but one internal read-only operation declared security: []. A single browser request then returned runtime data without authentication.
Calling Card
Client-Side Hard-Coded Bearer Token Exposure
Calling Card exposed a build-time bearer token in public JavaScript. Caido showed a 401 without the token and a 200 with it, while curl returned the same internal probe data.
Front Matter
Internal Endpoint Exposure
A production comment on the public Colophon page disclosed /api/internal/build and said it should remain off-network. Anonymous Caido and curl requests returned HTTP 200, build metadata, status ok, and the lab flag.