IT & Product
Vulnerability Disclosure
A responsible-disclosure intake for security researchers — severity, reproduction steps, and proof of concept in a shape your security team can triage.
- Questions
- 10
- Style
- One page
- Price
- Free
Vulnerability Disclosure
A responsible-disclosure intake for security researchers — severity, reproduction steps, and proof of concept in a shape your security team can triage.
Your name or handle (optional)
Contact email (optional)
Leave blank to report anonymously — but we can only send updates and credit if we can reach you.
Affected asset or URL*
Vulnerability class*
Describe the vulnerability class
Your severity estimate (CVSS-style)*
Your honest read — our team will do its own scoring during triage.
Steps to reproduce*
Numbered steps from a clean state. The faster we can reproduce it, the faster it gets fixed.
Proof of concept (optional)
Screenshots, a short video, or a PoC script (max 5 files, 25 MB each). Please redact any real user data.
How should we credit you? (optional)
Used in our security acknowledgments if the report is validated.
More IT & Product templates
Your name*
Your nameWork email*
Work emailIssue category*
Choose oneIT Support Ticket
A structured helpdesk intake — category, urgency, asset, and a clear description with an optional screenshot.
8 questionsOne page
Your name*
Your nameWork email*
Work emailSystem or application*
Choose oneAccess Request
Request system access with the justification, duration, and manager sign-off IT needs to approve it.
8 questionsOne page
Reported by*
Reported byWork email*
Work emailSeverity*
Option oneOption twoIncident Report
Log production incidents fast — severity, affected systems, start time, and impact in a consistent format.
8 questionsOne page
DataBoard templates
Start from a good first draft.
Pick the closest template, use it, and publish your own version, changed to fit.