Skip to content
Tutorials Center
My learning

Topics

Lesson 33 of 38 ยท Reporting

Writing Findings and Severity Ratings

Learn how to write a clear security finding from Burp evidence: title, description, impact, steps, remediation, and how to calculate a CVSS 3.1 base score.

A penetration test is only as valuable as its report. The client cannot fix what they cannot understand, and a brilliant exploit described badly gets ignored. A good finding is short, reproducible, honest about impact, and tells the developer what to change. This lesson shows how to turn Burp evidence into findings and how to rate their severity.

The Burp screens are labelled example output; the Python blocks are offline stand-ins.

Anatomy of a finding

Use the same structure for every issue so readers learn where to look:

Field What it says Tip
Title Name of the weakness and where "Stored XSS in order comments"
Severity Critical / High / Medium / Low / Info, with a score Justify it
Affected URL, parameter, role, version Exact, not "the website"
Description What is wrong, in two or three sentences Explain the root cause
Impact What an attacker could do in this business Concrete and honest
Steps to reproduce Numbered steps a developer can follow Include the request
Evidence Request/response excerpts, screenshots Redact secrets
Remediation What to change, with a reference Specific and actionable
References OWASP, CWE, vendor docs Optional but useful

A worked example

TEXT
Title: Missing object-level authorisation on /api/orders/{id}   (labelled example)
Severity: High (CVSS 3.1: 6.5 base - see below; business impact raises priority)
Affected: GET https://lab.example.test/api/orders/{id}, any authenticated user
Description: The endpoint returns any order whose id is supplied, without checking
  that the order belongs to the logged-in customer.
Impact: Any customer can read the name, address and items of every other customer's order
  by changing the id.
Steps:
  1. Log in as tester1 and open /orders/1001 (their order).
  2. In Repeater, change the id in GET /api/orders/1001 to 1002 (owned by tester2).
  3. Observe HTTP 200 and tester2's data.
Evidence: request/response pair, redacted (attachment A).
Remediation: Check order.customer_id == current user id on the server for every
  request (policy/middleware), and return 404 otherwise.

Notice the order-of-events steps use only test accounts, and the redaction: reports travel by email and get forwarded.

Writing rules that make findings useful

  • Write for two readers: an executive wants impact and risk; a developer wants steps and a fix.
  • Be specific, not scary. "An attacker can read other users' orders" beats "critical security failure".
  • One finding per root cause. If 12 endpoints share the same missing check, list the endpoints inside one finding.
  • Show, do not claim. Every claim has evidence you captured in Repeater or Logger.
  • Be honest about limits: what you did not test, and what you could not confirm.
  • Remove noise: do not paste whole scanner advisories or pages of raw output. Trim requests to the relevant lines.
  • Never include real secrets or live personal data. Mask tokens, passwords and personal data in screenshots.

Rating severity

Severity answers "how worried should we be, and what do we fix first?" Two ingredients: how easy the attack is, and how bad the result is. The common scale is CVSS (Common Vulnerability Scoring System). Version 3.1's base score uses eight metrics:

Metric Values
Attack Vector (AV) Network, Adjacent, Local, Physical
Attack Complexity (AC) Low, High
Privileges Required (PR) None, Low, High
User Interaction (UI) None, Required
Scope (S) Unchanged, Changed
Confidentiality (C) None, Low, High
Integrity (I) None, Low, High
Availability (A) None, Low, High

Score bands: 0.0 None, 0.1 to 3.9 Low, 4.0 to 6.9 Medium, 7.0 to 8.9 High, 9.0 to 10.0 Critical. (CVSS 4.0 exists with different metrics; many teams still quote 3.1. State which version you use.)

A CVSS 3.1 base-score calculator

This stand-in implements the published 3.1 formula for the base score, so you can see how each choice moves the result.

Python CVSS 3.1 base score (stand-in)

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

The four sample scores are 6.5 Medium, 9.8 Critical, 6.1 Medium and 3.1 Low, which match the published calculator for these vectors. Two points: CVSS rates the vulnerability in isolation, so add context (what data the system holds, whether it is internet-facing) when you set the final priority; and always show the vector string, for example CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, so others can reproduce your score.

Context adjustments

A "Low" cookie flag on a banking login might be treated as Medium; an IDOR on a public demo with fake data might drop. Explain adjustments in a Risk rating rationale line, and keep them consistent across the report.

Rate what you proved. If you only suspect something, label it "potential" with lower confidence rather than inflating severity. Your credibility is the report's most valuable asset.

Check your understanding

Quick check ยท 5 questions

of 5 answered You scored / 5 ยท perfect!

  1. 1. What should the Steps to reproduce section contain?

    Reproducible steps let the developer see and fix the problem.
  2. 2. How many findings should you write for 12 endpoints missing the same authorisation check?

    Grouping by root cause avoids noise and makes the fix clearer.
  3. 3. What does the CVSS Attack Complexity metric express?

    AC describes conditions the attacker cannot control that must exist for success.
  4. 4. Which belongs in a finding's evidence?

    Evidence should prove the issue while protecting sensitive data.
  5. 5. What score band is 7.5?

    7.0 to 8.9 is High.

Summary

  • A finding has title, severity, affected item, description, impact, steps, evidence and remediation.
  • Write for executives and developers; be specific, honest and one finding per root cause.
  • CVSS 3.1 combines eight base metrics into a score and band; show the vector string and explain context adjustments.
  • Rate what you proved, redact sensitive data, and keep wording consistent.
  • The finding text and calculator are labelled examples and offline stand-ins.

Next: Building the report and the re-test