About

About the range

An open, static, self-hosted training platform for learning web and application security through interactive capture-the-flag challenges.

Purpose

Reading about vulnerabilities is not the same as finding them. This range turns each OWASP Top 10:2025 risk into a hands-on scenario: you interact with a realistic simulated application, discover the weakness, exploit it to obtain a flag, and then study how to fix it. It is designed for students, developers, QA engineers and security newcomers, and works well in classrooms because it needs nothing but a web browser.

OWASP Top 10:2025 coverage

Each covered category has one Easy and one Medium challenge. This build includes 16 challenges across eight categories; A02 and A08 do not have challenges in this release.

A01

Broken Access Control

IDOR in a billing portal; cross-tenant data export in a SaaS API.

A02

Security Misconfiguration

Not included in this release.

A03

Software Supply Chain Failures

Typosquatted npm package; targeted payload in a transitive dependency.

A04

Cryptographic Failures

Encoding sold as encryption; repeating-key XOR broken with known plaintext.

A05

Injection

SQL injection tautology; UNION-based extraction with a filter bypass.

A06

Insecure Design

Negative-quantity checkout; gift card race condition (TOCTOU).

A07

Authentication Failures

Forgotten vendor service account; predictable password-reset tokens.

A08

Software or Data Integrity Failures

Not included in this release.

A09

Security Logging and Alerting Failures

Brute force below a broken alert threshold; suppressed audit events and log injection.

A10

Mishandling of Exceptional Conditions

Fail-open authorization; non-atomic transfer that crashes half-way.

Architecture

  • 100% static: HTML, CSS and vanilla JavaScript. No backend, database, build step or external dependency — upload the folder to any web host (including Hostinger shared hosting) and it works.
  • Simulations: each challenge mounts an isolated JavaScript model of an application (a browser, API console, terminal, SQL engine, SIEM…). Your input is interpreted by that model; nothing is executed or sent over the network.
  • Flag vault: challenge data contains no flags. Each flag is stored as a salted SHA-256 hash for verification, plus an XOR-sealed copy that the simulation can only unseal with a value it obtains once the vulnerability has been exploited.
  • Progress: stored in localStorage with an in-memory fallback when storage is unavailable.

Platform security

The challenges are intentionally vulnerable simulations, but the platform itself follows secure development practice: no eval() or dynamic code execution, no innerHTML with dynamic data (all rendering goes through a safe DOM builder and textContent), no inline event handlers, imported profiles are schema-validated, and the included .htaccess sends a strict Content Security Policy and other security headers.

Compatibility

Works in current versions of Chrome, Edge, Firefox and Safari on desktop, tablet and mobile, over HTTP or HTTPS. All paths are relative, so the site also works from a sub-folder.

Credits & disclaimer

Category names follow the OWASP Top 10:2025. This is an independent educational project and is not affiliated with or endorsed by the OWASP Foundation. All organisations, people and data in the scenarios are fictional. Learn more at owasp.org/Top10.