Cadence is a delivery-driver app. Registration takes a phone number, sends a six-digit code by SMS, and will not create the account until the code comes back.
You are registering with a number you do not control: +44 7700 900118. The code went to somebody else’s handset, so you do not have it and cannot get it.
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. Get the account verified without the code.
“The code field is always present, because our app always sends it.”
Treat an absent code as a failed verification rather than as nothing to check. Validate the shape of the body before branching on its contents, and make the success path something you have to reach deliberately rather than fall into.
Any check written as “if the field is here, compare it”: signature and HMAC verification, second-factor steps, CAPTCHA tokens, webhook validation. The tell is a guard nested inside a presence test, with no else.
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.