Documenting and Reporting Authorization Flaws
You'll learn: How to document authorization vulnerabilities in a way that clearly communicates risk and helps developers fix the problem.
Why Documentation Matters
Finding an authorization flaw is only half the battle. A poorly documented vulnerability report can lead to misunderstandings, incomplete fixes, or worse—dismissal of a legitimate security issue. Effective documentation bridges the gap between security testers and development teams, ensuring vulnerabilities get fixed properly.
Core Components of Authorization Flaw Reports
1. Proof of Concept (PoC)
Provide step-by-step reproduction instructions. For example, if you found an IDOR vulnerability:
- "User A logs in with account ID
123" - "User A changes parameter to ID
456in the profile endpoint" - "User A can now view/modify User B's data"
Include actual HTTP requests, parameters modified, and screenshots showing unauthorized access.
2. Impact Assessment
Clearly explain what an attacker could do:
- Access: What data or functionality becomes accessible?
- Scale: Can this affect one user or all users?
- Business Risk: Could this lead to data breaches, compliance violations, or financial loss?
Use severity ratings (Critical/High/Medium/Low) consistently.
3. Remediation Guidance
Don't just identify the problem—suggest solutions:
- "Implement server-side authorization checks before returning user data"
- "Validate that the authenticated user owns the requested resource ID"
- "Use indirect references or authorization tokens instead of direct IDs"
4. Context and Affected Components
Specify which endpoints, parameters, or workflows are vulnerable. This helps developers locate and fix issues quickly.
Key Takeaway: A well-documented authorization flaw includes clear reproduction steps, realistic impact assessment, and actionable remediation guidance—turning your finding into a security improvement.