Validation method / case archive

Authoritative Status Check

Confirm that the lab or application accepted the reproduced result.

Evidence boundary

The result reflects the authority and active instance represented by that status endpoint.

What it proves

That WebVerse accepted the recovered flag and recorded the challenge as solved.

What it does not prove

It does not replace the request, response, and runtime evidence explaining why the finding is valid.

Related classifications

Related entries

Archive connections

Connected case files

18 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-021WEBVERSE
Connected evidence

Knockdown

PHP Object Injection / Webroot File Write

A normal Knockdown export exposed a nested RenderCache object. Changing only its path and HTML properties produced one new PHP file in the webroot on two fresh instances.

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

ShippedSharp

JWT Signature Bypass / AI Tool SQL Injection

A member JWT was rejected by /admin, but the same claims with alg none and role admin opened the manager console. The report tool then accepted a controlled UNION query that reached one internal configuration value.

Browser / Caido / Python / curl
CASE-018WEBVERSE
Connected evidence

PrinPrin

Default Password / Administrative Access

An invalid login stayed on the public sign-in page, while admin/admin redirected to the printer dashboard. Caido and curl then reached the authenticated admin view and its remote service key.

Browser / Caido / curl
CASE-017WEBVERSE
Connected evidence

BookBomb

Path Traversal / Local File Read

A normal book download, a missing-file control, and a known public CSS comparison showed that the anonymous download handler accepted ../ path traversal and read local files outside its book directory.

Caido / Browser / curl
CASE-016WEBVERSE
Connected evidence

Larksong

Authenticated SSRF / Loopback Filter Bypass

An authenticated photo URL fetcher rejected 127.0.0.1 but accepted 2130706433. The sighting readback exposed internal response bodies and a clear live-versus-refused service difference.

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

Lumenex

JSON Query Operator Injection / Access-Control Filter Override

Lumenex accepted JSON query operators where its public search form sent strings. Changing status and visibility together returned an archived internal product, and the same result was reproduced in Caido and with curl.

Browser / Caido / curl / jq
CASE-013WEBVERSE
Connected evidence

Margin Notes

Missing Authentication / Public Source Map Disclosure

Margin Notes exposed a source map containing the route and response handling for a hidden diagnostic endpoint. One anonymous Caido request returned build data, runtime details, and the lab flag.

Browser / Caido
CASE-012WEBVERSE
Connected evidence

Flap Copy

Public Metadata Disclosure / Internal Route Exposure

Flap Copy’s landing page disclosed its PWA manifest. Comparing it with the public AASA file revealed an unadvertised staff route, and one request returned internal handoff details plus the redacted flag.

Caido / Chromium
CASE-010WEBVERSE
Connected evidence

LeakyPipe

SQLite SQL Injection / Verbose Error Disclosure

The public after filter on GET /reviews entered SQLite syntax. Because the page discarded query rows, a repeatable error/no-error check and a limited direct error leak were used to reach one internal configuration value before WebVerse accepted the flag.

Caido
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-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-006WEBVERSE
Connected evidence

DropCall

PostgreSQL Error-Based Blind SQL Injection

The public permit-search parameter accepted SQL syntax, allowing a one-column UNION and a repeatable conditional-error check. A focused extractor recovered the lab flag, which WebVerse accepted.

Caido / Chromium / Python
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-004WEBVERSE
Connected evidence

Front Matter

Internal Endpoint Exposure

A production comment on the public Colophon page disclosed /api/internal/build and said it should remain off-network. Anonymous Caido and curl requests returned HTTP 200, build metadata, status ok, and the lab flag.

Caido / 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.