- Anonymous responses include internal metadata, identifiers, or restricted status data.
- The disclosed information is tied to the active application instance.
Sensitive Information Disclosure
A public response reveals operational information beyond what the intended audience should receive.
Use a single anonymous read-only request, record only necessary fields, and redact flags, tokens, and reusable secrets.
Related entries
Connected case files
PrinPrin
Default Password / Administrative Access
An invalid login stayed on the public sign-in page, while admin/admin redirected to the printer dashboard. Caido and curl then reached the authenticated admin view and its remote service key.
Lumenex
JSON Query Operator Injection / Access-Control Filter Override
Lumenex accepted JSON query operators where its public search form sent strings. Changing status and visibility together returned an archived internal product, and the same result was reproduced in Caido and with curl.
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.
Tradesman
SQL Injection Authentication Bypass
SQL syntax in the legacy seller login changed a normal rejection into an admin session. Caido and curl both reached the linked administrators-only notes page.
Nolic
Authenticated Smarty SSTI to OS Command Execution
A public backup exposed an administrator SHA-256 digest. After recovering the password offline, I reproduced the Smarty SSTI and operating-system command execution in Caido and from the terminal. The original draft was restored after every test.
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.
Lobby Board
Anonymous Administrative Access
A public Next.js build manifest exposed a hidden admin route and its client chunk. The chunk identified /_admin/board with guard: null, and a request without Cookie or Authorization headers returned the genuine administrative submissions board.