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

Unsigned means sandbox

Medium Auth 3 Nov 2026

Scenario

Ridgeway Supply takes card payments through Paylink. When a payment settles, Paylink calls Ridgeway's callback and Ridgeway marks the order paid.

Paylink signs every callback with a timestamp and a MAC over the body. Ridgeway's integration guide has a section on testing against the callback without a live payment.

Order RW-2026-0441 is live and unpaid. The request below is a real Paylink callback you captured five days ago from a test purchase you made and refunded.

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:
X-Paylink-Signature:
event=&order=&amount=
No change — send it as it stands
Response

  • 01 What the server believed

    “A callback that verifies signatures is a callback that requires them.”

  • 02 The fix

    Treat a missing signature as a failed one and refuse. Give the sandbox its own endpoint, its own credentials and its own order store, so that a test callback cannot reach a live order whatever it says. Add a test that posts an unsigned callback for a live order and expects a refusal rather than a state change.

  • 03 Where else to look for this

    Anywhere verification has an else branch: unsigned requests treated as test traffic, a development mode enabled by the absence of a header, an API that accepts either signed or unsigned callers for backwards compatibility, a MAC checked only when the field is present. The pattern is the same as an optional CSRF token or an optional nonce. Before spending time on a signature, send the request without one and see which handler answers.

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