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

The verb in the body

Medium HTTP 29 Sep 2026 Solved by 2

Scenario

Brightloom distributes music. You are a label assistant: you maintain the revenue splits on a release, and removing a collaborator is a manager action.

The dashboard is server-rendered and every screen posts a form. This is one of them, sent when you change a split.

When you have tried a delete from a client of your own, the refusal was an HTML page with X-Edge-Rule: dash-destructive-verbs on it, rather than the JSON the dashboard returns for anything it declines itself.

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: laravel_session=
_method=&collaborator=&split=
No change — send it as it stands
Response

  • 01 What the server believed

    “The method a rule at the edge reads is the method the application will act on.”

  • 02 The fix

    Authorise the action in the handler, against the actor, so that no spelling of the request reaches a destructive path without a check. If the override is not needed, turn it off: Symfony ships it disabled and Spring disabled its filter by default for this reason. If it is needed, make the edge read it too, or move the rule inside the application where the effective method is known.

  • 03 Where else to look for this

    Anywhere the effective method is decided later than the rule that reads it: form method overrides in Laravel, Symfony and Rails, X-HTTP-Method-Override headers accepted by API gateways and SDKs, and RPC-style endpoints that take the operation from the body. The tell is a rule written in terms of verbs sitting in front of a framework that lets a request rename its own verb.

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