
In addition, PoC exploits serve as excellent documentation of the issue. This aids significantly in understanding how a vulnerability works and the potential risk it represents. It shows the vendor exactly what an attacker could do with their vulnerable API and helps them take remedial action. Simply put, a PoC exploit can help demonstrate the severity of an issue in ways that verbal descriptions cannot. So why is it important to write PoC exploits when reporting vulnerabilities?

All because the PoC exploit does most of the lifting in the reporting process. And most were shocked when they heard I rarely have more than a few messages back and forth with security triage. They were surprised I almost always include a working PoC for anything I report. As explained by one hacker, “I don’t want to get in trouble with the software vendor, and it’s too much effort.” Recently on Discord, I was discussing this with a few newer bug bounty hunters and was surprised to learn they don’t usually write a lot of PoC code themselves.
