r/Hacking_Tutorials • u/Sea_Manufacturer6590 • 3h ago
Question How to write a pentest finding a developer can actually fix
If you’re practicing in a lab or writing up your first authorized assessment, try this before you submit a finding: hand it to someone who wasn’t there for the test. Can they tell what happened, why it matters, and how to check the fix?
Here’s a simple structure I use:
- Name the behavior. Identify the affected feature and what it allowed. “A regular user could open another test account’s invoice” gives the reader more to work with than “broken access control.”
- Show the evidence. Include the relevant request and response with tokens, identifiers, and private data redacted. Use test accounts and keep only the evidence needed to establish the finding.
- State the impact you observed. If you confirmed that one invoice could be read, say that. Treat broader exposure as an open question until you have evidence.
- Give the developer a retest. In the invoice example, confirm that the owner can still open their invoice and that a separate account is denied access. That checks the fix and the legitimate workflow in one pass.
What’s one detail you wish people included more often in security reports?