Published · By the Aesparrow Security Research Team
Short answer
A web application VAPT checklist covers information gathering, configuration, authentication, session management, authorisation (IDOR and privilege escalation), input validation (SQL injection, XSS, command injection, SSRF, XXE), file uploads, business logic, cryptography, error handling and API security — aligned to the OWASP Top 10 and the OWASP Web Security Testing Guide.
What should a web application penetration test check?
- Information gathering: technologies, endpoints, hidden parameters, exposed files and subdomains.
- Configuration: security headers (CSP, HSTS), TLS, default pages, directory listing.
- Authentication: password policy, MFA bypass, brute-force protection, password reset flaws.
- Session management: cookie flags, token entropy, fixation, logout and timeout.
- Access control: IDOR, horizontal and vertical privilege escalation, forced browsing.
- Injection: SQL, NoSQL, OS command, LDAP and template injection.
- Cross-site scripting: reflected, stored and DOM-based XSS.
- Request forgery: CSRF and server-side request forgery (SSRF).
- XML and deserialisation: XXE and insecure deserialisation.
- File upload: type validation, path traversal, web-shell upload and malware.
- Business logic: price manipulation, workflow bypass, race conditions, rate limits.
- APIs: broken object-level authorisation, mass assignment and data exposure.
What is the OWASP Top 10?
The OWASP Top 10 is the Open Worldwide Application Security Project’s consensus list of the most critical web application security risks, such as broken access control, injection, cryptographic failures and security misconfiguration. It is the baseline most customers and auditors expect a web application penetration test to cover.

