Validation method / case archive

Browser Runtime Validation

Observe the final security-relevant behavior in a real browser execution environment.

Evidence boundary

The observation applies to the tested browser, page state, payload, and origin.

What it proves

That the constructed input produced the documented client-side runtime behavior.

What it does not prove

It does not prove support across every browser or apply the finding to untested sinks.

Related classifications

Related entries

Archive connections

Connected case files

06 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-020WEBVERSE
Connected evidence

RollWinded

Origin Validation Error / DOM XSS

The ScoreCast client accepted string messages without checking the sender origin or window. It then wrote the received string to innerHTML. A controlled sender opened the page, posted a small HTML payload, and changed the lab from unsolved to solved.

Browser / Caido / curl
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-011WEBVERSE
Connected evidence

Routing Slip

Missing Authentication / Sensitive Information Disclosure

Routing Slip’s developer portal linked the live OpenAPI file. Bearer authentication was required globally, but one internal read-only operation declared security: []. A single browser request then returned runtime data without authentication.

Browser / OpenAPI contract
CASE-007WEBVERSE
Connected evidence

Nolic

Authenticated Smarty SSTI to OS Command Execution

A public backup exposed an administrator SHA-256 digest. After recovering the password offline, I reproduced the Smarty SSTI and operating-system command execution in Caido and from the terminal. The original draft was restored after every test.

Caido / Chromium / Python / curl / Terminal
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.