Thornbury is a shared inbox for small teams. You are a member of the Ellis & Vane workspace. This is the lowest of its three roles: member, manager, owner. Members may invite other members, and that is all.
The invite form asks for an email and a name. It does not ask for a role, and the role column in the member list is not editable by you.
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. Create an invitation that arrives with more than member access.
“The body will only ever contain the fields our form renders.”
Allowlist email and name when creating invitations, and set the member role on the server. Put role changes behind a separate endpoint that checks whether the actor may assign the requested role, and reject unexpected fields.
Anywhere a handler builds a record straight from a request body: signup, profile updates, settings, invitations. The tell is a create or update call taking the body whole, or an allowlist written from the table’s columns rather than from what this caller may set.
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.