vuln-bank vs DVWA

Deliberately vulnerable security training apps compared

vuln-bank and DVWA provide deliberately vulnerable applications for practicing security testing in controlled environments. vuln-bank centers on banking workflows and covers web, API, GraphQL, and AI scenarios, while DVWA focuses on common web vulnerabilities with adjustable challenge difficulty.

vuln-bankDVWA
LanguageHTMLPHP
LicenseMITGPL-3.0
Stars96013.9k
Forks3485.2k
Last analyzedOct 3, 2026Oct 24, 2026

Key differences

  • vuln-bank includes banking features such as transfers, loans, and bill payments; DVWA presents common web vulnerability challenges through a straightforward web interface.
  • vuln-bank covers web, API, GraphQL, and AI security scenarios; DVWA offers documented and intentionally undocumented vulnerabilities, plus difficulty levels.
  • vuln-bank is listed with HTML and an MIT license; DVWA is built with PHP and MariaDB and uses GPL-3.0.
  • Both offer Docker Compose, but vuln-bank also documents a local Python/PostgreSQL path, while DVWA supports installation on a PHP/MariaDB web stack.
  • The provided repository figures list 960 stars and 348 forks for vuln-bank, compared with 13.9k stars and 5.2k forks for DVWA.

Choose vuln-bank if you…

  • need practice across banking workflows, APIs, GraphQL, and AI security scenarios.
  • want to review intentionally flawed application code or test security workflows against a banking-style app.
  • prefer a lab with a documented Docker Compose setup or local Python/PostgreSQL installation path.
Read the vuln-bank analysis →

Choose DVWA if you…

  • want a PHP/MariaDB lab focused on common web vulnerabilities.
  • need adjustable challenge difficulty or want to investigate intentionally undocumented vulnerabilities.
  • plan to use the app for classroom exercises or to test tools against a straightforward web interface.
Read the DVWA analysis →

Compare the numbers side by side, or add more projects

This comparison is generated with AI from the OSRepos analyses of both projects. Always check each project's repository and documentation before choosing.