Web for Ethical Hackers
Web hacking is testing web servers and applications for flaws, guided by the OWASP Top 10. SQL injection is a key example: unsanitised input changes the meaning of a database query. Testers also look at cross-site scripting, broken access control and misconfiguration, and recommend fixes such as parameterised queries.
Stage: Application and Platform Attacks · Part of the Ethical Hacker roadmap · Last reviewed 19 November 2026
What to learn in Web
- Intercept and modify requests with a proxy such as Burp Suite
- Detect and exploit a basic SQL injection in a lab and explain the root cause
- Fix SQL injection with parameterised queries instead of string concatenation
- Distinguish reflected, stored and DOM-based cross-site scripting
- Test for broken access control such as insecure direct object references
Web interview questions
How does SQL injection work and how do you prevent it?
When an application builds a query by concatenating user input, an attacker can add SQL syntax that changes the query's logic. Prevention is to use parameterised queries or prepared statements, which send data separately from code, plus least-privilege database accounts.
What is the difference between stored and reflected XSS?
In reflected XSS the malicious script comes from the request and is immediately echoed in the response, so a victim must follow a crafted link. In stored XSS the script is saved on the server and runs for every user who views the content.
Where Web fits in the Ethical Hacker roadmap
Web belongs to the Application and Platform Attacks stage (intermediate level), which takes about 34 hours. Web, mobile and cloud.
Other units in this stage
Back to the full Ethical Hacker roadmap