- Library
- IT & Data Center
- Web Application Penetration Testing Checklist
Web Application Penetration Testing Checklist
36 questions in 6 sectionsInteractive preview: try the answers
Section 1 of 6 · 6 questionsReconnaissance & Attack Surface Mapping
Can the application’s domains, subdomains, APIs, and admin panels be fully enumerated?
Can the technology stack and frameworks be identified from the outside?
Can hidden or undocumented endpoints be discovered?
Can development, staging, or internal environments be accessed?
Can sensitive files or configuration endpoints be found?
Can the application’s main business workflows be mapped from the outside?
Section 2 of 6 · 6 questionsAuthentication & Session Attacks
Can authentication be bypassed under any circumstances?
Can multi-factor authentication be bypassed or abused?
Can weak or default credentials be used to log in?
Can the password reset or account recovery flow be abused?
Can user sessions be hijacked, fixed, or reused?
Do sessions remain valid after logout or password change?
Section 3 of 6 · 6 questionsAuthorization & Access Control Bypass
Can a normal user access another user’s data by modifying IDs or parameters?
Can a normal user access admin or internal functionality?
Can privileges be escalated by manipulating requests or roles?
Are backend APIs enforcing authorization independently of the UI?
Can object-level permissions be bypassed through direct API calls?
Can internal or hidden features be accessed without proper rights?
Section 4 of 6 · 6 questionsInjection, Input Handling & File Attacks
Can SQL injection, NoSQL injection, or command injection be triggered?
Can reflected, stored, or DOM-based XSS be triggered?
Can file upload restrictions be bypassed to upload dangerous files?
Can path traversal be used to access unauthorized files?
Can CSRF protections be bypassed or are they missing?
Can template injection or deserialization attacks be triggered?
Section 5 of 6 · 6 questionsBusiness Logic & Workflow Abuse
Can application workflows be abused to skip required steps?
Can business rules be bypassed to gain free credits, refunds, or approvals?
Can race conditions be exploited to duplicate or manipulate transactions?
Can pricing, quantities, or approval states be manipulated in requests?
Can limits or quotas be bypassed through request manipulation?
Can the same operation be abused repeatedly for unintended gain?
Section 6 of 6 · 6 questionsInfrastructure, API & Exploitation Chaining
Can API endpoints be abused through mass assignment or object injection?
Can API rate limits be bypassed or abused?
Can secrets, tokens, or credentials be found in client-side code or responses?
Can misconfigured infrastructure or cloud services be accessed?
Can multiple low-severity issues be chained into a full account takeover or data breach?
Can attacks be performed without triggering meaningful alerts or logs?
Checklist by GoAudits. This checklist is an example: we do not guarantee compliance with the laws applicable to your territory or industry. Seek professional advice to adapt it to your workplace or jurisdiction.
Free PDF
Download the Web Application Penetration Testing Checklist
By downloading this checklist you agree to the GoAudits privacy policy and terms of service.
NEW! Try generating a custom checklist with our free AI tool:
Easy inspection app for your digital checklists
- Conduct inspections anytime, anywhere - even offline
- Capture photos as proof of compliance or areas needing attention
- Instantly generate and share detailed reports after the inspections
- Assign & track follow-up tasks, view historical trends on a centralized dashboard