Every finding answers four questions.
What is wrong. How we proved it. What it costs you. The exact change that closes it.
- where
- POST /login, Set-Cookie header
- proof
- document.cookie returns the session value
- impact
- Any script injection becomes account takeover
- fix
- Set-Cookie: session=...; HttpOnly; Secure; SameSite=Lax
- status
- fixed, retested
What is in the report.
Five parts, in the order you will read them.
- 01
Summary
One page for the people who decide: what we tested, what we found, what to do first.
- 02
Scope and method
Exactly what was in and out of scope, and how we tested it.
- 03
Findings
Each issue with severity, location, proof, and impact in plain terms.
- 04
Fixes
A specific change for every finding, written for your stack.
- 05
Retest
The status of each finding after your fixes, checked by running the attack again.
How we rank severity.
Severity is about impact on your business, not about how clever the bug is.
Direct compromise of accounts or data with no special conditions. Fix before anything else ships.
Serious impact that needs one condition to be met, such as a logged-in user or a crafted link.
Limited impact, or hard to exploit in practice. Plan it into the next release.
Hardening and good practice. Worth doing, not urgent.
Got something to build, or something to break?
Tell us what it is. A few lines are enough to start.