[ R2 ]   Competition review / Fall 2026

A payload worked.
Did the filter notice?

We replay three rounds of the classroom XSS and SQL injection arena. Every attack below was proved by the judge and reached at least one other player.

01 / The shape of the game

Three rounds. Two different outcomes.

The first round rewarded direct browser events and SQL UNION queries. As triggered defenses became shared rules, the surviving attacks changed shape.

Only attacks that passed at least one defender appear here. Counts are submissions, so repeated payloads count separately.

The SQL side closed early. SQL injection had 48 breakthrough submissions in round 1 and none in rounds 2 or 3. Two shared rules matched a quote followed by SELECT and vault across line breaks. XSS still had two breakthroughs in round 2 and seven in round 3.

02 / Complete annotated archive

Every successful payload, explained.

Every submission uses the same view: the exact payload, highlighted parser steps, and a numbered explanation. Repeated submissions remain visible because each was tested against the other players.

Parser boundary Trigger or query Proof target

Loading attacks…

Mixed payloads may have several execution paths. The annotations explain a visible path.

03 / Defenses in the wild

What each rule actually caught.

Each rule blocked an attack for some players even though that same submission reached someone else. The counts measure first-rule blocks among the successful submissions on this page.

For browser content

Put text in text positions.

Context-aware output encoding or a maintained HTML sanitizer prevents input from becoming executable markup. A blocklist has to guess every browser interpretation.

For database queries

Keep values out of SQL syntax.

Parameterized queries give the database the SQL structure and user value separately. A blacklist is tied to the current query and table names.