Infosec Institute

Open Bug Bounty mentioned in the
Top 6 Bug Bounty programs of
2022 by the InfoSec Institute

The Hacker News

Open Bug Bounty named among the
Top 5 Bug Bounty programs of 2021
by The Hacker News

All Open Bug Bounty emails are sent only from openbugbounty.org domain being digitally signed. All others are fake. Learn more.
For security researchers
Report a Vulnerability
Submit, help fixing, get kudos.
For website owners
Start a Bug Bounty
Run your bounty program for free.
1,440,565 coordinated disclosures
1,087,533 fixed vulnerabilities
1,733 bug bounty programs, 3,421 websites
33,362 researchers, 1,518 honor badges

Wisr.com.au Bug Bounty Program

Wisr.com.au runs a bug bounty program to ensure the highest security and privacy of its websites. Everyone is eligible to participate in the program subject to the below-mentioned conditions and requirements of Wisr.com.au

Open Bug Bounty performs triage and verification of the submissions. However, we never intervene to the further process of vulnerability remediation and disclosure between Wisr.com.au and researchers.

Bug bounty program allow private submissions only.

Bug Bounty Scope

The following websites are within the scope of the program:

*.wisr.tech
*.wisr.com.au

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

General Requirements:

Wisr wants to find vulnerabilities in its customer-facing API (https://apis.sandbox.wisr.tech/)

Please include a working PoC, attach screenshots, postman collections, and anything else that will make bug verification simple. Remediation guidelines are welcome.

Testing Requirements:

To begin with, please limit yourself to https://apis.sandbox.wisr.tech/

See documentation at https://apis-docs.sandbox.wisr.tech/index.html

Generally speaking, any bug that poses a significant vulnerability to the security or integrity of the Wisr ecosystem could be eligible for a reward. However, it is entirely at our discretion to decide whether a bug is significant enough to be eligible for a reward.

In general, anything which has the potential for financial loss or data breach is of sufficient severity, including

* Implementation bugs that can lead to financial loss
* Access to our production servers
* Remote Code Execution
* Crash bug in our APIs (e.g., a bug that can crash the app by sending a special request, not by sending thousands of requests)

In general, the following would not meet the threshold for severity:

* Recently disclosed 0-day vulnerabilities.
* Vulnerabilities on sites hosted by third parties unless they lead to a vulnerability on the main website
* Vulnerabilities contingent on physical attack, social engineering, spamming, DDOS attack, etc.
* Vulnerabilities affecting outdated or unpatched browsers
Vulnerabilities in third-party applications that make use of Wisr’s APIs
* Bugs that have not been responsibly investigated and reported
* Bugs already known to us or already reported by someone else (reward goes to the first reporter)
* Issues that aren’t reproducible
* Issues that we can’t reasonably be expected to do anything about

Possible Awards:

Wisr will provide monetary awards for vulnerabilities.

The amount of the award depends on the degree of severity of the vulnerability reported.

The Wisr Bug Bounty Panel will evaluate award sizes according to the severity calculated by Open Bug Bounty. However, final awards are determined at the sole discretion of the panel.

Special Notes:

You must discuss any vulnerabilities found with Wisr first.

Community Rating

Provided by security researchers who reported security vulnerabilities via this bug bounty program:

 
Response Time  Information How quickly researchers get responses to their submissions.
Remediation Time  Information How quickly reported submissions are fixed.
Cooperation and Respect  Information How fairly and respectfully researchers are being treated.

Researcher's comments

No comments so far.

  Latest Patched

 08.02.2023 moqawmh.ps
 07.02.2023 nt.am
 05.02.2023 dcfs.louisiana.gov
 05.02.2023 asrock.com
 05.02.2023 itaxi.ws
 05.02.2023 sexchat.ws
 05.02.2023 mekamebel.mebeli.ws
 05.02.2023 altibbi.com

  Latest Blog Posts

16.01.2023 by itsvarmakollu
XSS vulnerabilities discovered in ServiceNow - CVE-2022-38463
16.01.2023 by itsvarmakollu
Turning cookie-based XSS into account takeover
08.07.2022 by 4websecurity
CVE 2022-29455 is still affecting millions of Wordpress sites
08.07.2022 by kh4sh3i_
Zabbix - SAML SSO Authentication Bypass
08.07.2022 by FR13ND0x7F
The Time Machine — Weaponizing WaybackUrls for Recon, BugBounties , OSINT, Sensitive Endpoints and what not

  Recent Recommendations

@benschrijver     7 February, 2023
    Twitter benschrijver:
Rajesh pointed out several XSS issues with our application and offered helpful pointers to resolve them.
@rinconensalza     7 February, 2023
    Twitter rinconensalza:
Thank you for helping me to find some bugs on my web, very appreciated!!
@mb_mbit     4 February, 2023
    Twitter mb_mbit:
Many thanks to KhanJanny for responsibly disclosing an XSS vulnerability on some of my websites. Highly recommended professional!
@nidapo5     4 February, 2023
    Twitter nidapo5:
Jitin spotted an XSS vulnerability in a minor input field on one of our pages, and reported it clearly, so I could easily spot the problem and fix it. Many thanks for this help.
@uTechJeremy     3 February, 2023
    Twitter uTechJeremy:
Thank you for your assistance addressing a bug!