A practical, documentation-first playbook for web vulnerability hunting.
Methodologies, checklists, and reproducible test cases for pentesters, bug bounty hunters, and AppSec teams.
HowToHunt is a structured collection of web security testing guidance focused on execution, not just theory.
This repository helps you answer, consistently:
- What to test
- How to test
- What to validate
- How to reproduce findings clearly
Use it as a field manual for:
- Web application penetration testing
- Bug bounty assessments
- Security lab training
- Internal application security reviews
- Step-by-step methodologies for common web vulnerability classes
- Practical test cases with reproducible validation flow
- Checklist-driven coverage to reduce missed attack paths
- Tool-agnostic Markdown documentation
- Friendly for beginners, useful for experienced testers
- Easy to adapt for personal workflows or team playbooks
This is a documentation repository — no build process or runtime setup is required.
Open and browse the Markdown files directly in this repository.
git clone https://github.com/adminsairolotech-bit/HowToHunt.git
cd HowToHuntOpen files with any Markdown editor/viewer (VS Code, Obsidian, Typora, etc.).
For a book-style reading experience:
- Select a target scope (authorized only).
- Pick a vulnerability category from the docs.
- Follow methodology + checklist during testing.
- Execute test cases and capture evidence.
- Document reproducibility steps for each confirmed finding.
- Report with impact, proof, and remediation guidance.
The repository is organized as Markdown-based guidance and test notes.
Use folder/file names as your navigation map by vulnerability category and test flow.
Contributions are welcome and encouraged.
You can help by:
- Improving methodology clarity
- Adding new test cases
- Expanding edge-case coverage
- Fixing inaccuracies or outdated guidance
- Improving formatting and readability
- Fork the repository
- Create a feature branch
git checkout -b docs/improve-xss-methodology - Commit your changes with clear messages
- Push to your fork
- Open a Pull Request with:
- What you changed
- Why it improves testing quality
- Any references/examples
Please keep contributions:
- Ethical and legal
- Focused on defensive security testing and authorized assessments
- Reproducible and clearly written
This project is licensed under the GNU General Public License v3.0.
See the LICENSE file for full details.