Write a report

Bug bounty impact statement

A bug bounty impact statement says who can do what to whom, under which conditions, and with what result. Write the facts yourself, then let AI tighten the wording without adding claims.

Updated November 18, 2026By bugbountyai

Who

Any signed-in user

Does what

reads

To whom

other users' invoices

Under which conditions

by changing the invoice ID

With what result

name, address and order history exposed

Before and after

BugBeforeAfter
IDORAttacker can access sensitive data.Any signed-in user can read another user's invoices, including name, address and order history, by changing the invoice ID. The victim does nothing.
Stored XSSXSS can lead to account takeover.Script saved in a profile bio runs in the session of any signed-in user who opens the profile, including support staff. I did not test account changes.
Exposed debug pageServer leaks information.An unauthenticated /debug page on api.example.com lists internal service names and a database host.

What HackerOne asks

"Explain the potential consequences of the vulnerability, including how an attacker could exploit it and what damage it could cause."

HackerOne, Quality Reports, read November 18, 2026

Claim only what your proof shows, and name what you did not test.

The prompt

Prompt
Tighten this impact statement.Keep every fact. Add none.Remove any claim my PoC notes do not support, and list what you removed. <impact>[your draft]</impact><poc>[your PoC notes]</poc>