One Request Away No. 23 Streak 0 Solved 0 of 27

Approved on arrival

Medium Priv Esc 13 Oct 2026 Solved by 2

Scenario

Fenwick Mulberry runs an expenses desk. A claim is raised by the person who spent the money, approved by their line manager, and paid in the weekly run.

You are a contractor. You can raise claims and you cannot approve them. The claim list shows a coloured pill against each row: submitted, then approved, then paid.

This is the request the new claim form sends.

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.

Request Tap any part of it
// HTTP/1.1
Host:
Content-Type:
Cookie: fmx_session=
{
"amount": ,
"category": ,
"note":
}
No change — send it as it stands
Response

  • 01 What the server believed

    “Fields the form does not offer are fields a request cannot set.”

  • 02 The fix

    Bind an explicit allowlist on create: amount, category and note, and nothing else. Set the workflow state in the handler rather than from input, and make the transition to approved a separate, authorised operation that records who performed it. Add a test that posts a claim with a status field and expects it to be created as submitted.

  • 03 Where else to look for this

    Anywhere a create or update binds a request body onto a model with more columns than the form has inputs. The famous version sets a role or an is_admin flag; the quieter and often more valuable version sets a workflow state, a verification flag, a tier, a balance, an expiry, or a foreign key that moves the record into somebody else's scope. The vocabulary is usually printed in the interface as a status label.

The series

Every drill 27

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.

Do not stop here

A drill is one request.
A lab is the whole app.

Uphack labs are believable products with one realistic flaw buried in an ordinary feature. Same instinct, nothing highlighted — you get a running application and have to find it yourself.

Browse the labs
Registration is open Closes today

Turn the instinct into practice.

Drills are free and stay that way. The labs put the same reasoning against a whole application, and members get all of them. Registration is open until Saturday 19 September.

Create your account

Already a member? Sign in