Lab / Manual PTK proof

One author, another viewer

Use the loopback runtime and two isolated browser contexts. The prepared marker changes only this local page's DOM attribute; do not use a remote payload.

  1. Setup: as Alice, save the page's prepared local proof in the review route. Start Bob in the second context with Full PTK IAST active.
  2. One action: Bob presses Load as viewer.
  3. Vulnerable outcome: Bob's page interprets the saved markup and sets document.documentElement.dataset.storedXss to executed.
  4. Repaired outcome: Bob presses the same button on the repaired route; the exact message appears as literal text and no proof attribute is set.

Reset: send an authenticated POST /api/labs/reset on the local runtime or restart it, then recreate Alice's message. Use fresh isolated contexts for a new run.

Exact PTK evidence claim: manual Full browser/Proxy proof links Alice's stored POST, Bob's GET and the differing DOM result. An IAST/SAST automatic finding is only claimed after its exact native Full positive/control export is verified.

All labs