Free tool · no signup

Pentest report template generator

Enter the engagement details and your findings and get a structured penetration test report in Markdown: executive summary, scope, method, findings table, details and fix priorities.

By the Bug Circuit security team · Last updated

The engagement

Finding 1

  • Add the client name.
  • Add the target, for example the main website address.
Your report (Markdown)
Add the client and the target to see the report.
  • No findings yet. The report is built with an empty findings section, which is valid for a test that found nothing.
  • Remove any real credentials, tokens or customer data from the steps and evidence before you share the report.

Paste the Markdown into your editor of choice, or into a Markdown to PDF converter, and add your logo. Nothing you type here leaves your browser.

What goes in a pentest report? A short summary for decision makers, the scope and method, a table of findings by severity, and for each finding the evidence, the impact and the exact fix. Fill in the form, copy the Markdown and add your logo. Nothing leaves your browser.

How it works

The structure that works

A report has two audiences. The first page is for the person who decides and pays: what was tested, how risky the result is and what to do first, in plain words. The rest is for the engineer who fixes things: which URL, how to reproduce it, and the change to make. Mixing the two is the most common reason a report gets read once and ignored.

The template follows that order: document details, executive summary with a severity count, scope and approach, methodology, a summary table, remediation priorities, then one section per finding with description, impact, steps to reproduce, remediation and references, and a note on retesting.

Rating severity

Give every finding a severity, and where you can, a CVSS 3.1 vector, which turns the judgement into a number: Critical 9.0 to 10.0, High 7.0 to 8.9, Medium 4.0 to 6.9, Low 0.1 to 3.9. Paste the vector and the report shows the score, and warns you when it disagrees with the severity you picked. CVSS ignores business context, so a medium score on your payment page can deserve a high rating. Say so in the finding and explain why.

Writing findings people can act on

One finding is one problem with one fix. Say where it is, show how to reproduce it in numbered steps, state the impact in terms of what an attacker gets, and give a specific remediation, not "sanitise input". Keep evidence tight: a request and a response beat ten screenshots. Remove real passwords, tokens and customer data before the report leaves your hands. After the client fixes things, retest each finding and record the result.

Worked examples

Executive summary

Three findings: one critical, one high, one low.

The test found 3 issues: 1 critical, 1 high, 1 low. The overall risk is critical. The critical and high issues should be fixed first, as set out in section 5.

The generator counts the findings by severity and writes this paragraph for you, so it always matches the table below it.

The summary table

The same three findings, sorted by severity.

| ID | Finding | Severity | CVSS | Affected |
|---|---|---|---|---|
| F-01 | SQL injection in the search box | Critical | 9.8 (Critical) | https://example.com/search |
| F-02 | Customers can read each other's invoices | High | n/a | /account/invoices/{id} |
| F-03 | Security headers missing | Low | n/a | All pages |

Findings are numbered after sorting, so F-01 is always the one to fix first.

A vector and the score it gives

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CVSS 3.1: 9.8 (Critical)

Network attack, low complexity, no privileges, no user interaction, full impact on confidentiality, integrity and availability.

Frequently asked questions

What format should a pentest report be in?
Most clients expect a PDF. Write it in Markdown here, paste it into your editor or a Markdown to PDF converter, and add your logo and a cover page. Keep an editable copy for the retest.
Should I use CVSS or my own rating?
Use CVSS as a starting point because clients and auditors recognise it, then adjust for business context and explain the difference. A report that only says "high" with no reasoning is hard to defend.
How long should a report be?
As long as the findings need and no longer. A small web test is often 10 to 25 pages. A long report with little in it is worse than a short one with clear fixes.
Do I include screenshots?
Include evidence that proves the finding, such as the request and response, and a screenshot only where it shows something text cannot. Crop out anything private.
What should I remove before sharing a report?
Real credentials, session tokens, API keys and customer data that appeared during testing. Replace them with placeholders. Share the report only with the people who need it, because it lists the weaknesses of a live system.
What is a retest?
After the client fixes the findings, you test each one again and record whether it is resolved. Many clients and auditors want proof of the retest, so leave room for it in the report.
Where can I see a finished report?
Our sample report shows a complete one with evidence and fixes, written for a small business site.

Keep reading

See what attackers see, for free

Run the free passive check on your website. No login, no impact on your site, results in seconds.

Ready for the full manual audit? See pricing

Pentest Report Template Generator · Bug Circuit