Code reviews, but for HTTP requests. Each day you get one real request that is a single change away from an exploit. Spot the value the server shouldn't trust, change it, and send it.
Two minutes, and the whole thing happens in the browser.
A legitimate request, exactly as the client sent it. Somewhere in it is one part the server shouldn't trust. Nothing is marked; click the part you suspect.
Pick what to do with it: substitute it, remove it, add to it, or switch the method. Every drill is solved with one of these four moves, one change per send.
Send it and read what comes back: a status, a body, and a short note on why. The right change triggers the issue. A wrong one gets an honest answer too, and that is usually the lesson.
Newest first. Each one names the request it is about, so you can pick by what you want to practise.
No drills match that.
Try removing a filter.