Skip to main content
  1. Learning/
  2. Resources/

The Web Application Hacker's Handbook

Author
CodeBrew
CodeBrew shares practical security research, defensive engineering notes, and portfolio projects.

Overview
#

Written by the founders of PortSwigger, the company behind Burp Suite, WAHH is the text that taught a generation how web applications break. It works through the attack surface methodically, covering application mapping, client-side control bypasses, and attacks against authentication, session management, access controls, data stores, and the back end. Each vulnerability class gets an explanation of the underlying mechanism before the attack is demonstrated.

That mechanism-first structure is the reason it is still recommended. Much web security content teaches payloads. WAHH explains why a payload works, which is the knowledge that leads to finding bugs a wordlist would miss.

How It’s Used
#

  • As a conceptual layer under hands-on practice. Reading a chapter and then working the corresponding PortSwigger Web Security Academy labs pairs explanation with proof of understanding.
  • The methodology chapter. The closing testing checklist is the most immediately applicable section, offering a structured approach to assessing an application rather than probing it ad hoc.
  • As reference beside a syntax-oriented resource such as the web cheatsheet, which covers the command detail the book does not need to repeat.

Strengths & Limitations
#

The free successor is the better starting point. The second edition dates to 2011, and the authors have effectively superseded it with the Web Security Academy, which is free, browser-based, continuously updated, and covers modern vulnerability classes the book predates entirely: SSRF, insecure deserialization, HTTP request smuggling, modern CORS misconfiguration, JWT attacks, and prototype pollution. PortSwigger maintains a page mapping the book’s chapters onto Academy topics.

That inverts the way this book is usually recommended. The Academy is the primary resource, and WAHH is optional supplementary reading for chapters where a longer prose treatment is useful, particularly access control, session management, and methodology.

Anything covering specific Burp workflows is over a decade out of date and can be skipped. What holds up is the reasoning about why an application trusts input it should not, and that has not changed.

Not the right fit if: budget is constrained or the reader is new to web security. The free Academy is the stronger starting point in essentially every case. The book is worth revisiting only when a deeper written treatment of a specific topic is wanted.

Details
#