Security pattern / case archive

Context-Specific Output Encoding Failure

Attacker-controlled data is emitted without the encoding required by its exact HTML output context.

Common discovery signals
  • The same input is encoded differently across text and attribute sinks.
  • A context delimiter survives reflection and changes document structure.
Safe validation approach

Map each sink separately and begin with harmless delimiter and canary payloads before any controlled runtime proof.

Related classifications

Related entries

Archive connections

Connected case files

03 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.

Caido / Browser / curl
CASE-001WEBVERSE
Connected evidence

Echoed

Reflected XSS

The q parameter was reflected into two HTML contexts. A raw double quote broke out of the search input value attribute, enabling attacker-controlled autofocus and onfocus attributes and browser-side JavaScript execution.