- Restricted routes respond successfully without the expected authorization context.
- Publicly disclosed resources lead to functions intended for a narrower audience.
Broken Access Control
A server-side authorization boundary does not prevent an unauthorized client from reaching protected data or functionality.
Use a minimal anonymous or lower-privilege request and compare it with the documented access expectation without modifying protected state.
Related entries
Connected case files
ShippedSharp
JWT Signature Bypass / AI Tool SQL Injection
A member JWT was rejected by /admin, but the same claims with alg none and role admin opened the manager console. The report tool then accepted a controlled UNION query that reached one internal configuration value.
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.
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.
Dust Jacket
Sensitive Backup and Credential Exposure
An Apache directory listing exposed config.php.bak with a reusable OWNER_KEY. The owner console rejected an invalid key but accepted the exposed value without Cookie or Authorization headers.
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.