Raising and managing GitHub issues - Port Swigger
Summary: PortSwigger's documentation describes how Burp Suite DAST raises or links GitHub issues so fixes can be tracked in GitHub, requiring an administrator to first add a connection and set up an action that defines the repository and fields. The body of a raised issue ends with a hidden HTML comment named burp-suite-correlation-id that must not be removed, and DAST warns when an action may create a duplicate of an issue it already raised on the same connection and repository.
Bottom line: Comments DAST adds when linking or unlinking include the Burp Suite issue title, its URL and your name, and GitHub has no private comments - so anyone who can read the repository, or everyone in the GitHub enterprise for an internal repo, sees them, and no comment is added at all in a public repository.
Read the original at PortSwigger Research ↗
- Topics
- Vulnerabilities & Patching
- Related
- Attackers Exploit UnrealIRCd Flaw That Enables Server-Level Command Injection Cyber Risks · Nov 14, 2026U.S. CISA adds Check Point and UnrealIRCd flaws to its Known Exploited Vulnerabilities catalog Cyber Risks · Nov 14, 2026PostgreSQL Patches 52 Flaws, Including 22-Year-Old Bug Enabling Authenticated RCE Cyber Risks · Nov 13, 2026