Coordinated and Responsible Vulnerability Disclosure Free Bug Bounty Program 329,606 coordinated disclosures
191,020 fixed vulnerabilities
415 bug bounties with 872 websites
9,243 researchers, 854 honor badges

Are you sure you want to delete the vulnerability?

Yes No

This feature enables you to send additional notifications to the website owners or admins after the vulnerability is submitted. The total number of additional notification is limited to 10, and to 1 in 24 hours.

Notify specific security contact:

To my best knowledge this email belongs to the website owner/admin

Open Bug Bounty ID: OBB-754246

Security Researcher Gh05tPT Helped patch 3777 vulnerabilities
Received 9 Coordinated Disclosure badges
Received 28 recommendations
, a holder of 9 badges for responsible and coordinated disclosure, found a security vulnerability affecting website and its users.

Following coordinated and responsible vulnerability disclosure guidelines of the ISO 29147 standard, Open Bug Bounty has:

      a. verified the vulnerability and confirmed its existence;
      b. notified the website operator about its existence.

Technical details of the vulnerability are currently hidden ("On Hold") to give website operator/owner sufficient time to patch the vulnerability without putting any of its systems or users at risk. Once patched, vulnerability details can be publicly disclosed by the researcher in at least 30 days since the submission. If for a reason the vulnerability remains unpatched, its details can be disclosed only 90 days.

Open Bug Bounty Program:Create your bounty program now. It's open and free.
Vulnerable Application:[hidden until disclosure]
Vulnerability Type:XSS (Cross Site Scripting) / CWE-79
CVSSv3 Score:[hidden until disclosure]
Disclosure Standard:Coordinated Disclosure based on ISO 29147 guidelines
Discovered and Reported by:Gh05tPT Helped patch 3777 vulnerabilities
Received 9 Coordinated Disclosure badges
Received 28 recommendations
Remediation Guide:OWASP XSS Prevention Cheat Sheet

Coordinated Disclosure Timeline

Vulnerability Reported:11 February, 2019 16:24 GMT
Vulnerability Verified:11 February, 2019 16:39 GMT
Website Operator Notified:11 February, 2019 16:39 GMT
a. Using the ISO 29147 guidelines
b. Using publicly available security contacts
c. Using Open Bug Bounty notification framework
d. Using security contacts provided by the researcher
Public Report Published
[without any technical details]:
11 February, 2019 16:39 GMT
Scheduled Public Disclosure:  A security researcher can delete the report before public disclosure, afterwards the report cannot be deleted or modified anymore. The researcher can also postpone public disclosure date as long as reasonably required to remediate the vulnerability.12 May, 2019 16:24 GMT

For Website Operators and Owners

Please contact the researcher directly to get the vulnerability details. The researcher may also help you fix the vulnerability and advice on how to prevent similar issues:

For remediation best practices, please also refer to OWASP remediation guidelines. More information about coordinate and responsible disclosure on Open Bug Bounty is available here.

DISCLAIMER: As a non-profit project, Open Bug Bounty never acts as an intermediary between website owners and security researchers. Our role is strictly limited to independent verification of the reports and proper notification of website owners by all available means.

Website Overview

Alexa Global Rank:N/A
SSL/TLS Server Test:A    View Results
Web Server Security Test:F    View Results
Malware Test:Click here
Domain Health Report:Click here

Latest Submissions

OBB-ID Reported by Status Reported on
On Hold

  Latest Patched


  Latest Blog Posts

22.03.2019 by HackerGautam
TLS 1.3 Genesis, Mechanism and Working
19.03.2019 by Open Bug Bounty
GDPR PII exposure can now be securely reported via Open Bug Bounty
24.02.2019 by ismailtsdln
Apple XSS Vulnerability - Proof of Concept (PoC)
24.02.2019 by ismailtsdln
How do you use an xss as a keylogger ?
23.02.2019 by ismailtsdln
Everything about XSS is in this source!

  Recent Recommendations

    26 March, 2019
Thanks for fing the vulnerability. Bug will be fixed at next update.
    25 March, 2019
Brian has responsibly reported a misconfiguration on one of my servers that could have led to sensitive information disclosure. He clearly and quickly explained the issue and its potential implications, and made it clear he did not expect anything for this.

Brian is a true internet hero, we need more people like Geeknik. Thanks a lot for making the internet safer.
    25 March, 2019
Dear Armin, thank you very much for reporting a vulnerability to us in such a respectful, professional way! Your extensive documentation helped us tremendously to solve the issue in almost no time.

It's guys like you that make the internet a better and safer place! Thanks alot!
    25 March, 2019
Thank you very much for reporting, you helped us a lot - fixed.
    24 March, 2019
Thank you for reporting this vulnerability to us responsibly and for your professional conduct. Your assistance and professionalism is much appreciated.