Web Application Penetration Testing Checklist

Use this Web Application Pen Testing Checklist to find vulnerabilities in authentication, APIs, input handling, and business logic. Test your app against real-world attack scenarios, save this test record for compliance and audit-readiness.

Web Application Penetration Testing Checklist



Reconnaissance & Attack Surface Mapping

1. Can the application’s domains, subdomains, APIs, and admin panels be fully enumerated?


Photo Comment

2. Can the technology stack and frameworks be identified from the outside?


Photo Comment

3. Can hidden or undocumented endpoints be discovered?


Photo Comment

4. Can development, staging, or internal environments be accessed?


Photo Comment

5. Can sensitive files or configuration endpoints be found?


Photo Comment

6. Can the application’s main business workflows be mapped from the outside?


Photo Comment
Authentication & Session Attacks

1. Can authentication be bypassed under any circumstances?


Photo Comment

2. Can multi-factor authentication be bypassed or abused?


Photo Comment

3. Can weak or default credentials be used to log in?


Photo Comment

4. Can the password reset or account recovery flow be abused?


Photo Comment

5. Can user sessions be hijacked, fixed, or reused?


Photo Comment

6. Do sessions remain valid after logout or password change?


Photo Comment
Authorization & Access Control Bypass

1. Can a normal user access another user’s data by modifying IDs or parameters?


Photo Comment

2. Can a normal user access admin or internal functionality?


Photo Comment

3. Can privileges be escalated by manipulating requests or roles?


Photo Comment

4. Are backend APIs enforcing authorization independently of the UI?


Photo Comment

5. Can object-level permissions be bypassed through direct API calls?


Photo Comment

6. Can internal or hidden features be accessed without proper rights?


Photo Comment
Injection, Input Handling & File Attacks

1. Can SQL injection, NoSQL injection, or command injection be triggered?


Photo Comment

2. Can reflected, stored, or DOM-based XSS be triggered?


Photo Comment

3. Can file upload restrictions be bypassed to upload dangerous files?


Photo Comment

4. Can path traversal be used to access unauthorized files?


Photo Comment

5. Can CSRF protections be bypassed or are they missing?


Photo Comment

6. Can template injection or deserialization attacks be triggered?


Photo Comment
Business Logic & Workflow Abuse

1. Can application workflows be abused to skip required steps?


Photo Comment

2. Can business rules be bypassed to gain free credits, refunds, or approvals?


Photo Comment

3. Can race conditions be exploited to duplicate or manipulate transactions?


Photo Comment

4. Can pricing, quantities, or approval states be manipulated in requests?


Photo Comment

5. Can limits or quotas be bypassed through request manipulation?


Photo Comment

6. Can the same operation be abused repeatedly for unintended gain?


Photo Comment
Infrastructure, API & Exploitation Chaining

1. Can API endpoints be abused through mass assignment or object injection?


Photo Comment

2. Can API rate limits be bypassed or abused?


Photo Comment

3. Can secrets, tokens, or credentials be found in client-side code or responses?


Photo Comment

4. Can misconfigured infrastructure or cloud services be accessed?


Photo Comment

5. Can multiple low-severity issues be chained into a full account takeover or data breach?


Photo Comment

6. Can attacks be performed without triggering meaningful alerts or logs?


Photo Comment

Is this sample what you are looking for?
Sign up to use & customise this template, or create your own custom checklist:

Checklist by GoAudits.com – Please note that this checklist is intended as an example. We do not guarantee compliance with the laws applicable to your territory or industry. You should seek professional advice to determine how this checklist should be adapted to your workplace or jurisdiction.

Easy inspection app for your digital checklists