Report a Vulnerability
Submit, help fixing, get kudos.
Start a Bug Bounty
Run your bounty program for free.
533,913 coordinated disclosures
288,533 fixed vulnerabilities
742 bug bounties with 1,457 websites
15,010 researchers, 1072 honor badges

  Please, login via Twitter first




Start Bug Bounty Program in 5 Easy Steps. It's Free!

Start Your Bug Bounty Program at Open Bug Bounty

Open Bug Bounty allows any verified website owners to run a bug bounty for their websites at no cost. The purpose of this non-profit activity is to make relations between website owners and security researchers sustainable and mutually beneficial in a long-term prospective.

Starting a bug bounty is free and open to everyone. Once logged in via Twitter, you can create your bug bounty program in a few minutes and get unlimited access to our security researchers. Once a vulnerability is reported, you will get instant notification to coordinate disclosure and remediation with researcher.

Open Bug Bounty does triage and verification of the submissions. However, we never intervene to the further process of your communication with the researchers, vulnerability remediation and disclosure. Once a vulnerability is verified and reported to you, our role in coordinated disclosure process is over.

For website owners, we provide vulnerability data export option to the following SDLC, DevOps and bug tracking systems:

  Bugzilla

  Splunk

  JIRA

  Mantis

General

Please carefully fill-in the form below to launch your bug bounty:

This will be a name under which your bug bounty will be displayed. Please use meaningful and relevant name to better guide the researchers.

Please read about type of vulnerability submissions and select the best one for you:

   Researchers will be able to submit both private and public submissions.
   Researchers will be able to submit private submissions only.

We will send notifications for domains from your scope to these email addresses. We do not share these email addresses with anybody.

Bug Bounty Scope

You will need to confirm your website ownership by placing a special security.txt file on it:

Non-Intrusive Submissions Handling

The following section encompasses submission of the vulnerabilities that do not require intrusive testing as per Open Bug Bounty rules:

- Cross Site Scripting (XSS)
- Open Redirect

- Cross Site Request Forgery (CSRF)
- Improper Access Control

Please specify your Vulnerability Disclosure Program requirements. They will be displayed to security researchers:

Please specify technical or any other reasonable requirements for submissions (e.g. exclusion of self-XSS). Please specify any special requirements for testing methodologies (e.g. restriction to use vulnerability scanners). Please specify which rewards you may provide to the researchers who follow the above-mentioned requirements (e.g. recommendation in researcher's profile, mention in a Hall of Fame or something more valuable proportional to the researcher's efforts). Anything else you would like to bring to the attention of researchers community.

Other Submissions Handling

Open Bug Bounty does not accept security vulnerabilities that may require some sort of intrusive testing to be detected (e.g. SQL injection). Therefore, we do not accept, verify or store them on our platform. Nevertheless, as a website owner, you can specify how and where to report them if ever you wish them to be reported.



Please specify where and how (e.g. email) these vulnerabilities may be sent. You can provide your public PGP key here to encrypt the notifications sent via a method you specify above. Please specify technical or any other reasonable requirements for submissions (e.g. exclusion of self-XSS). Please specify any special requirements for testing methodologies (e.g. restriction to use vulnerability scanners). Please specify which rewards you may provide to the researchers who follow the above-mentioned requirements (e.g. recommendation in researcher's profile, mention in a Hall of Fame or something more valuable proportional to the researcher's efforts). Anything else you would like to bring to the attention of researchers community.

Need Any Help?

Need any help or have any questions about the bug bounty? The community forum is here to help!

  Latest Patched

 07.04.2020 axure.com.cn
 07.04.2020 apu.edu
 07.04.2020 sermoncentral.com
 07.04.2020 dinakaran.com
 07.04.2020 ranker.com
 06.04.2020 ac-grenoble.fr
 06.04.2020 prefeitura.sp.gov.br
 06.04.2020 cmb.fr
 06.04.2020 cdiscount.com

  Latest Blog Posts

04.04.2020 by Rando02355205
(Alibaba) message.alibaba.com [IDOR] - [Bug Bounty]
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

  Recent Recommendations

    7 April, 2020
     Rumskkurs:
Thanks Rajesh, for reporting some vulnerabilities of our site! Useful reports and good communication.
    6 April, 2020
     chris05634528:
Jatin understood the importance of moving quickly and with discretion. He waited to until he found the right group to submit the details and provided easy-to-understand details.

As a result we have remediated the problem and have Jatin to thank.
    5 April, 2020
     christophmoar:
Cool and professional contact, quick response, I appreciate your effort.
Thanks!
    3 April, 2020
     KenDennis:
Brian helped to identify an XSS Vuln on a client's wordpress implementation and was quick and helpful to respond to our query. With his notes, we were able to quickly mitigate this issue and we appreciate his help and professionalism.
    2 April, 2020
     EmanuelePisapia:
I have really appreciated this researcher for his great skill and communication. He found a cross site scripting vulnerability on our service and help us fixing it. I recommend Broly157. He's a A++ researcher