Report a Vulnerability
Submit, help fixing, get kudos.
Start a Bug Bounty
Run your bounty program for free.
531,773 coordinated disclosures
287,511 fixed vulnerabilities
732 bug bounties with 1,447 websites
14,900 researchers, 1070 honor badges

How create xml report file via Burp Suite

1. Reproduce the vulnerability using Burp Suite

2. Proxy - HTTP History tab should contain at least 3 HTTP requests

  • First request with page contents for CSRF exploitation
  • Second request – the actual exploitation of CSRF vulnerability
  • Third request with page contents after CSRF exploitation

3. Add comments to request, as shown below


4. Select the requests and save them into file


5. Send the saved file using report form.

  Latest Patched

 01.04.2020 litnet.com
 01.04.2020 repubblica.it
 01.04.2020 emcitv.com
 01.04.2020 nw.de
 01.04.2020 web.fnal.gov
 31.03.2020 smccd.edu
 31.03.2020 apostilasopcao.com.br
 31.03.2020 savings.com
 31.03.2020 jezebel.com
 31.03.2020 suruga-ya.jp

  Latest Blog Posts

12.03.2020 by Rando02355205
(Paypal) www.paypal.com [CSP High Level] - [XSS Reflected] - [Bug Bounty] - [Write Up]
08.03.2020 by CybeReports
JDECO.net XSS Vulnerability| CybeReports
29.02.2020 by Rando02355205
(Google) groups.google.com - [Stored XSS] - [Bug Bounty] - [WriteUp] - [24/02/2020]
10.02.2020 by 0xrocky
Stored XSS on h2biz.net
10.02.2020 by ismailtsdln
SQL Injection Payload List

  Recent Recommendations

    31 March, 2020
     reinisroz:
Thanks much, anguhari, for providing detailed information about XSS bug, found on our website. Highly recommended and professional security researcher!
    31 March, 2020
     admonaut:
Many thanks for your support and assistance. Good job :-)
    31 March, 2020
     thisismeraul:
Thanks for finding this vulnerability for us. The corporate website is more secure now. Good job!
    31 March, 2020
     reinisroz:
Thanks researcher for pointing out the problems in our website.
    31 March, 2020
     aylab:
Thank you for informing me of the issue you found and being so thorough with your details, finding and fixing the problem would have been hard without it.