Pellerin sells design assets in several countries. You are buying one licence from its UK store, listed at £890.
The checkout collects the purchase details, billing country, display language, promotion code, and payment method. This is the request it 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.
Hint. Complete the purchase for much less than £890.
“Protecting the amount is enough, even when the client controls the currency.”
Store amount and currency together and load both from the server-side price record. If customers may select a currency, load a server-defined price for that currency or convert the amount on the server. Reject unexpected pricing fields and test that changing currency cannot keep the same amount.
Check checkout, refunds, payouts, top-ups, wallet credits, and regional price lists. Look for an amount loaded by the server while its currency, unit, or exchange rate comes from the request.
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.