gitwtfhub

wtf is waes?

0verflowme/waes — explained in plain English

Analysis updated 2026-07-29 · repo last pushed 2019-07-30

Audience · developerComplexity · 2/5DormantSetup · moderate

TL;DR

A one-click bash tool that automatically chains together common security scans, firewall detection, vulnerability checks, HTTP header analysis, and directory fuzzing, against a target website and saves all results to a report folder.

Mindmap

mindmap
  root((repo))
    What it does
      Firewall detection
      Vulnerability scanning
      HTTP header checks
      Directory fuzzing
    Tech stack
      Bash scripting
      Nmap
      Nikto
      Dirb
    Use cases
      CTF challenges
      Hack The Box boxes
      Security practice
    Audience
      Security enthusiasts
      CTF participants
    Design choices
      Single threaded
      Bash not Python
    Roadmap
      SSL scanning
      CMS detection

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Why would anyone build with this?

REASON 1

Run a single command to scan a Hack The Box machine and collect all security findings in one folder.

REASON 2

Automate repetitive website security checks like port scanning, header analysis, and hidden directory discovery.

REASON 3

Chain nmap, nikto, and dirb scans together automatically for a new CTF target IP and port.

What's in the stack?

BashNmapNiktoDirb

How it stacks up

0verflowme/waes00kaku/gallery-slider-block04amanrajj/netwatch
Stars0
LanguageJavaScriptRust
Last pushed2019-07-302021-05-19
MaintenanceDormantDormant
Setup difficultymoderateeasymoderate
Complexity2/52/53/5
Audiencedevelopergeneralops devops

Figures from each repo's GitHub metadata at analysis time.

How do you spin it up?

Difficulty · moderate Time to first run · 30min

Requires nmap, nikto, and dirb to be installed on your system before running the tool.

Wtf does this do

CPH:SEC WAES is a one-click tool that automatically scans a website for security information and saves the results into files. Instead of running multiple scanning tools one at a time against the same target, you point this tool at an IP address and let it handle the entire process. It was built mainly for people doing capture-the-flag (CTF) hacking challenges on platforms like Hack The Box, where running the same routine scans over and over gets tedious. When you launch a scan, the tool moves through four stages. It starts with firewall detection and a quick network map, then moves into deeper scanning that checks for known vulnerabilities, examines HTTP headers, and looks for cross-site scripting issues. Finally, it fuzzes the target, essentially guessing hidden web pages and directories by running through large wordlists of possibilities. Everything it discovers gets dumped into a report folder so you can review the findings. The primary users are security enthusiasts and CTF participants who want to skip the repetitive setup of tools like nmap, nikto, and dirb. For example, if you start a new Hack The Box machine at 10.10.10.130 on port 8080, you run a single command and the tool chains those scans together for you, saving the manual effort of configuring and running each one separately. One notable design choice is that the tool deliberately avoids multi-threaded scanning. The author points out that while parallel scanning might seem faster, it tends to crash or hang the target machines, especially in CTF environments. The project is also written in bash rather than Python, which the author chose as an exercise in building a solid bash project. The tool is currently aimed at CTF-style boxes but is moving toward broader online use, with features like SSL scanning and CMS detection on the roadmap.

Yoink these prompts

Prompt 1
Help me install and run WAES against a Hack The Box target at 10.10.10.130 on port 8080. Walk me through the one-command scan and where to find the report folder.
Prompt 2
I want to understand what WAES scans for in each of its four stages: firewall detection, vulnerability scanning, HTTP header checks, and directory fuzzing. Summarize what each stage does.
Prompt 3
Compare WAES to running nmap, nikto, and dirb manually. What are the trade-offs of using a single bash tool versus running each scanner separately for CTF challenges?
Prompt 4
Help me review the WAES report output files after a scan completes. What should I look for first when triaging findings for a CTF box?

Frequently asked questions

wtf is waes?

A one-click bash tool that automatically chains together common security scans, firewall detection, vulnerability checks, HTTP header analysis, and directory fuzzing, against a target website and saves all results to a report folder.

Is waes actively maintained?

Dormant — no commits in 2+ years (last push 2019-07-30).

How hard is waes to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is waes for?

Mainly developer.

View the repo → Decode another repo

This repo across BitVibe Labs

Don't trust strangers blindly. Verify against the repo.