- Backup configuration files are served as source text.
- The exposed values map to live application components or consumers.
Sensitive Configuration Disclosure
A publicly reachable artifact reveals configuration values or operational secrets that should remain outside the public boundary.
Capture only the minimum evidence, redact secret values, and verify relevance without publishing reusable credentials.
Related entries
Connected case files
ThePoint
Public Configuration File / Sensitive Information Disclosure
A public .env file returned the application key, mail settings, and database configuration. The key contained the WebVerse objective, which the platform accepted.
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.
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.
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.
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.
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.