Security pattern / case archive

Stored XSS

User-controlled content is stored and later runs as script when another browser renders it.

Common discovery signals
  • A public submission is later shown in an authenticated review page.
  • A callback reports the protected page path and title after the stored item is viewed.
Safe validation approach

Start with a small callback that reports only the page context. Do not take cookies or reusable credentials.

Related classifications

Related entries

Archive connections

Connected case files

02 records
CASE-022WEBVERSE
Connected evidence

Smoothie

Stored XSS / Output Encoding Failure

An inert HTML marker exposed different username handling across two sinks. A stored img/onerror payload then set a local DOM marker and changed the lab status from unsolved to solved.

Browser / Caido / Chromium DevTools
CASE-015WEBVERSE
Connected evidence

Owners

Stored XSS / Dangerous File Upload

Owners chained Stored XSS in the staff message viewer with an unsafe avatar upload. The staff browser kept its own session, .php and .php.jpg provided the controls, and .phtml returned the redacted lab proof.