WebExploitGym — Vulnerable Apps

A collection of 33 real-world, self-hostable vulnerable web applications, each pinned at the commit of a specific CVE (2025–2026 disclosures). Deploy any one with a single command and get a live, exploitable instance of the vulnerable version — useful for exploit development, agent evaluation, training, and security research.

Layout

targets/<name>_<CVE>/
  meta.yaml    CVE id, vulnerable version + commit, vulnerability class, effect, host port,
               endpoint path, starting privilege
  deploy/      docker-compose.yml pinned to the vulnerable image/build + up.sh (one-command deploy)
  source/      the application source AT THE VULNERABLE COMMIT (.git stripped — the fix is not shipped)
registry.tsv   index of all targets (project / CVE / version / commit / effect)

Host a target

cd targets/databasir_CVE-2025-66944/deploy
bash up.sh
# → the vulnerable app is now live on the host port named in ../meta.yaml (e.g. localhost:8301)

Most targets pull a pinned public image; a few build from the bundled source/ (need network at build time for Maven/npm/pip). up.sh also seeds any demo state (admin account / sample data) needed to reach the vulnerable surface.

What each app is vulnerable to

meta.yaml records the CVE, the affected version/commit, and the effect class — spanning file read/write, SQL injection / database read & modification, authentication bypass, privilege escalation, SSRF / data exfiltration, and remote code execution. See registry.tsv for the full list at a glance.

Scope & caveats

• Vulnerable by design. These are intentionally insecure, pinned-vulnerable apps. Run them only in an isolated/sandboxed network — never expose them to the public internet.
• Source is at the vulnerable commit, with .git removed so the patch/fixed tags are not leaked.
• Reference exploit PoCs and the effect-oracle/evaluation harness are not included here (kept separate so this stays a clean, hostable app collection).

Licensing

Each targets/*/source/ tree is third-party open-source software and retains its upstream license (see the source's own LICENSE file). Packaging metadata (meta.yaml, deploy/, registry.tsv) is released under the project license. license: other reflects this mix.

Provenance

All CVEs are 2025–2026 disclosures (anti-memorization). Source is pinned at the vulnerable commit; see registry.tsv for per-target CVE / version / commit.