Security Vulnerability
Security vulnerability reports come from automated scanners, penetration testers, and bug bounty researchers in vastly different formats. This template normalises them into affected component, vulnerability type, CVSS-style severity, attack vector, proof of concept, and recommended remediation, enabling your security team to triage and prioritize consistently.
See it in action
What users type
What you get
Jake Underwood
jake@whitehatsec.io
IDOR
GET /api/v2/forms/:formId/submissions
High
Authenticated users can access other organisations' form submissions by incrementing formId parameter. No rate limiting. PII exposure confirmed across 15 organisations from test account.
Add organisation-scoped authorisation checks on all resource endpoints; implement rate limiting
Extracted fields
| Field | Type | Required |
|---|---|---|
| Reporter | text | Required |
| Required | ||
| Vulnerability Type | select | Required |
| Affected Component | text | Required |
| Severity | select | Required |
| Description | text | Required |
| Recommended Remediation | text | Optional |
Use this template
Sign up and select “Security Vulnerability” from the template gallery. Customise any field before going live.
Start with this template — freeRelated
Templates
Parse bug reports from users or QA into structured tickets with reproduction steps and severity.
Change RequestStructure change requests with scope, justification, risk assessment, and rollback plan.
Incident PostmortemStructure incident postmortem narratives into timeline, root cause, impact, and action items.