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

Platform update: please use our new authentication mechanism to securely use the Open Bug Bounty Platform.
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,703,146 coordinated disclosures
1,382,536 fixed vulnerabilities
1,989 bug bounty programs, 3,917 websites
46,834 researchers, 1,651 honor badges

ClickMeeting Bug Bounty Program

ClickMeeting 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 ClickMeeting

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

Bug bounty program allow private and public submissions.

Bug Bounty Scope

The following websites are within the scope of the program:

*.clickwebinar.com
*.clickmeeting.com

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:

Always provide details of the security issue including all information needed to reproduce and validate the vulnerability and also you should provide a Proof of Concept (POC).

If you check the security of our service, you can not bring negative results or any other problems with data security, data disclosure or providing our service.

You can not modify, obtain, disclose, delete or share information that does not belong to you.
After reporting security issue, give us a reasonable time to fix the problem before you making any information public.

In particular, we ask you to refrain from testing resistance to any type of denial of service attacks, social engineering attacks, any other brute force attacks and others non-qualifying issues.

Testing Requirements:

QUALIFYING ISSUES
We qualify reporting issues regarding OWASP Top 10, in particular for one of the categories:
- Injection
- Broken authentication
- Sensitive data exposure
- XML external entities (XXE)
- Broken access control
- Security misconfiguration
- Cross-site scripting (XSS)
- Insecure deserialization
- Using components with known vulnerabilities
- Insufficient logging and monitoring

NON QUALIFYING ISSUES
We do not qualify reporting issues, in generally, regarding for one of the categories:
- Physical or Social Engineering
- Phishing Attack
- Mixed-content scripts
- Insecure cookies
- Vulnerabilities that require a potential victim to install non-standard software
- Service banner disclosure
- Vulnerabilities affecting users of outdated or unsupported browsers or platforms
- Self-XSS which cannot be used to exploit other users
- Reports from automated tools or scans
- Denial of Service Attacks
- Host Header Injection
- Reflected File Download (RFD)
- Username Enumeration
- Content injection issues
- Cross-site Request Forgery (CSRF) with minimal security implications (Logout CSRF, etc.)
- Missing autocomplete attributes
- Missing cookie flags
- Issues which require physical access to a victim’s computer
- Missing security headers which do not present an immediate security vulnerability
- SSL/TLS scan reports
- Open ports without an accompanying proof-of-concept demonstrating vulnerability
- Open Redirect Vulnerabilities
- Publicly accessible login panels
- Recently disclosed 0-day Vulnerabilities
- Email/SMS flooding attacks
- Issues related to software or protocols not under our control
- Clickjacking and the issues exploited only by clickjacking
and others Vulnerabilities out of scope OWASP Top 10.

Possible Awards:

You will always get our gratitude. At present we do not offer any other awards.

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

S3CUR1TY101     29 July, 2019
    S3CUR1TY101:
how can i contact you in regarding to stored xss i found stored xss in your site

  Latest Patched

 19.04.2024 mlsi.gov.cy
 18.04.2024 recycleright.sa.gov.au
 17.04.2024 maps.bolton.gov.uk
 16.04.2024 fishwatch.gov
 16.04.2024 renewableenergy.gov.bd
 13.04.2024 lit.am
 13.04.2024 overnewton.vic.edu.au

  Latest Blog Posts

04.12.2023 by BAx99x
Unmasking the Power of Cross-Site Scripting (XSS): Types, Exploitation, Detection, and Tools
04.12.2023 by a13h1_
$1120: ATO Bug in Twitter’s
04.12.2023 by ClumsyLulz
How I found a Zero Day in W3 Schools
04.12.2023 by 24bkdoor
Hack the Web like a Pirate: Identifying Vulnerabilities with Style
04.12.2023 by 24bkdoor
Navigating the Bounty Seas with Open Bug Bounty

  Recent Recommendations

    10 April, 2024
    Mars:
Hatim uncovered a XSS bug that we were able to quickly resolve. Thanks very much for your assistance and help.
    8 April, 2024
    Panthermedia:
Thanks to the support of Hatim Chabik, we were able to identify and solve an XSS bug.
    5 April, 2024
    pubpharm:
Pooja found a XSS vulnerability on our website and provided us with the needed Information for replication and fixing the issue. Which she verified afterwards.
We thank her for the reporting and assistance.
    2 April, 2024
    genoverband:
Thank you for your invaluable help in ensuring the security of our domain and its visitors!
    20 March, 2024
    TechVitaverdura:
Great exchanges with this person, thank you for your help and your report