Validation method / case archive

Consumer Mapping

Trace a disclosed value to the exact endpoint, field, or code path that consumes it.

Evidence boundary

The mapping shows the intended relationship in the reviewed artifact, not live acceptance.

What it proves

Where and how the application expects the identified value to be supplied.

What it does not prove

It does not show that the value still works until the live endpoint is tested.

Related classifications

Related entries

Archive connections

Connected case files

04 records
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-009WEBVERSE
Connected evidence

Bothered

Second-Order SQL Injection

A self-created account stored a SQL-significant username that was interpreted only when the authenticated history page reused it. Caido captured the error, boolean, UNION, and final solved-state checks.

Caido / Chromium
CASE-005WEBVERSE
Connected evidence

Calling Card

Client-Side Hard-Coded Bearer Token Exposure

Calling Card exposed a build-time bearer token in public JavaScript. Caido showed a 401 without the token and a 200 with it, while curl returned the same internal probe data.

Caido / curl
CASE-003WEBVERSE
Connected evidence

Dust Jacket

Sensitive Backup and Credential Exposure

An Apache directory listing exposed config.php.bak with a reusable OWNER_KEY. The owner console rejected an invalid key but accepted the exposed value without Cookie or Authorization headers.