vuln-report

Generate a complete vulnerability report by inputting a security finding to produce a standardized output containing a header, executive summary, technical description, reproduction steps, evidence, impact assessment, and remediation guidance.

Format reproduction steps and evidence using standardized templates that guide the attachment of redacted screenshots, logs, and CVSS or CWE references to ensure consistent language across bug bounty reports.

Yes, you can use this across security testing projects, bug bounty programs, and internal audits to produce consistent vulnerability reports that clearly communicate risk and remediation to technical and non-technical stakeholders.

Structure the vulnerability report using a standardized template that separates the technical description and reproduction steps from the executive summary, impact assessment, and remediation guidance to clearly communicate risk to developers.

A complete vulnerability report should include a header, executive summary, technical description, reproduction steps, evidence, impact assessment, and remediation guidance to effectively communicate findings to stakeholders.

Providing CVSS and CWE references is recommended as part of the evidence handling guidelines to ensure the vulnerability report meets standardized security testing and auditing requirements.