Lab / Manual PTK proof
Update another user's order
Use the loopback runtime with separate synthetic Alice and Bob browser contexts. Capture Alice's POST in Full PTK Proxy; the authorization check must bind the selected order to the session, not merely validate the note.
- Setup: open the review route as Alice, select Bob's order and enter a distinct short note.
- One action: press Update order.
- Vulnerable outcome: Alice gets HTTP 200; Bob reads his order in his own context and sees the changed note.
- Repaired outcome: the same cross-owner POST on the repaired route returns 403 and Bob's note stays unchanged; Bob's own update still works.
Reset: while signed in, call the Playground's documented POST /api/labs/reset from the local browser/session, or restart the local runtime. Check Bob's original note before repeating.
Exact PTK evidence claim: manual Proxy/Request Builder proof pairs Alice's captured POST with Bob's observed changed/unchanged object. No automatic BOLA finding is claimed without a native Full export.