vuln-report

/vuln-report

Write a professional vulnerability report for bug bounty platform submission with clear reproduction steps, accurate severity assessment, and impact analysis.

Trigger

Use when you have confirmed a vulnerability and need to write a clear, professional report for submission. Also useful for:

• Reviewing and improving a draft report before submission
• Escalating a finding by demonstrating higher impact
• Writing a retest report after a fix has been deployed
• Documenting a vulnerability chain combining multiple findings

Input

• Vulnerability type: What class of vulnerability (XSS, IDOR, SSRF, SQLi, etc.)
• Affected asset: Exact URL, endpoint, or application component
• Description: What you found and how it works
• Reproduction steps: How you triggered the vulnerability
• Evidence: HTTP requests/responses, screenshots, PoC code
• Impact assessment: What an attacker could achieve
• Program context: Which bug bounty program, any relevant program-specific information
• Severity estimate: Your initial assessment of severity

Process

1. Title crafting -- Write a specific, descriptive title that communicates the vulnerability type, location, and impact in one line. Examples:

   • Good: "Stored XSS via SVG upload in profile avatar allows session hijacking on app.example.com"
   • Bad: "XSS found"
   • Good: "IDOR in /api/v2/users/{id}/documents allows any authenticated user to download other users' documents"
   • Bad: "Authorization bypass"

2. Summary writing -- 2-3 sentences covering: what the vulnerability is, where it exists, and the maximum impact. This is what the triage analyst reads first.

3. Reproduction steps -- Write exact, numbered steps that work on the first attempt:

   • Start with prerequisites (account type, browser, extensions needed)
   • Every step must be specific: exact URLs, exact input values, exact clicks
   • Include the expected vs actual result
   • Provide raw HTTP requests for precision