You are signed in to the Brightmoor supplier portal as Dana Whitfield, accounts payable at Brightmoor Retail. You have just opened one of your own invoices.
Yesterday the portal emailed you a payment reminder that was not meant for you. It referenced invoice INV-4468, raised against a company called Ashcroft Freight. You have never had an account with them.
One change to this request triggers the vulnerability. The challenge is to use your security intuition to work out what to change. Find the value the server shouldn’t trust, change it, and send it. The response tells you whether you were right.
Hint. Make this request return a record that does not belong to Brightmoor.
“Anyone holding a valid session is entitled to any invoice they can name.”
Query by both invoice reference and the authenticated user’s server-side organisation ID, returning 404 when no record matches. Enforce the rule in a shared authorisation policy and add a cross-organisation integration test.
Anywhere an identifier travels in a URL and the handler’s first act is to look it up: invoice and order detail endpoints, document downloads, message threads, export jobs. The tell is a handler that fetches by id and returns, with no second query about the caller.
One Request Away is a daily series of challenges. They’re like code review, but for HTTP requests: in each one you’re one request away from triggering a vulnerability, and your goal is to identify what you need to change.