Labs / XSS

Five paths to browser execution

Every working lab has one prepared action, a vulnerable and repaired route, a harmless execution marker, and reset instructions. A browser marker proves the target contrast—not an automatic PTK finding. Full and Auto findings are labelled only after native qualification.

Server-reflected contexts

Browser target verified · PTK finding pending

HTML body reflection

Query data is interpreted as HTML versus encoded text.

Open lab
Browser target verified · PTK finding pending

Quoted attribute breakout

The same input leaves a server-rendered attribute only on the vulnerable route.

Open lab

Stored, two-session

Browser target verified · Full proof pending

Alice writes; Bob reads

A separate browser session renders stored content; the repaired route treats it as text.

Open lab

DOM source-to-sink

Browser target verified · PTK finding pending

Fragment → innerHTML

The page reads location.hash and reaches an HTML sink.

Open lab
Browser target verified · PTK finding pending

Query → JavaScript execution

The page reads location.search and constructs code; the control renders text.

Open lab

SPA and multi-context candidates

These existing paired missions have source-to-sink evidence, but have not yet passed separate harmless-script-execution and current Full-finding qualification for this XSS collection. They are not counted among the five execution labs.

Short-lived SPA notice

Hash query data reaches a 30 ms DOM notice.

Open mission

Saved workspace

Persisted storage data reaches a later document.

Open mission

Loaded profile preview

A fetched response field reaches a DOM renderer after a user action.

Open mission

Support widget message

Cross-window message data reaches a widget renderer.

Open mission

Pro-only targets will be marked Pro — coming soon only after the target works and its private rule mapping is verified. This page does not imply unpublished Pro detection is available.

All lab categories · Playground home