Coordinated and Responsible Vulnerability Disclosure Free Bug Bounty Program 257,516 coordinated disclosures
153,998 fixed vulnerabilities
207,982 websites, 17,225 VIP websites
6,879 researchers, 6,915 subscribers

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

Security Researcher AndreCalvinho Helped patch 3826 vulnerabilities
Received 10 Coordinated Disclosure badges
Received 29 recommendations
, a holder of 10 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.

Open Bug Bounty Program:Create your bounty program now. It's open and free.
Vulnerable Application:Custom Code
Vulnerability Type:XSS (Cross Site Scripting) / CWE-79
CVSSv3 Score:6.1 [CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N]
Disclosure Standard:Coordinated Disclosure based on ISO 29147 guidelines
Discovered and Reported by:AndreCalvinho Helped patch 3826 vulnerabilities
Received 10 Coordinated Disclosure badges
Received 29 recommendations
Remediation Guide:OWASP XSS Prevention Cheat Sheet

Vulnerable URL:


Screenshot:  vulnerability

Mirror: Click here to view the mirror

Coordinated Disclosure Timeline

Vulnerability Reported:20 May, 2018 11:18 GMT
Vulnerability Verified:20 May, 2018 11:33 GMT
Website Operator Notified:20 May, 2018 11:33 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]:
20 May, 2018 11:33 GMT
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.18 August, 2018 11:18 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:F    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

  Latest Patched
    Patched on 21.08.2018
    Patched on 21.08.2018
    Patched on 21.08.2018
    Patched on 21.08.2018
    Patched on 21.08.2018
    Patched on 21.08.2018
    Patched on 21.08.2018
    Patched on 20.08.2018
    Patched on 20.08.2018
    Patched on 20.08.2018

  Recent Recommendations

    21 August, 2018
Andre found out a vulnerability on our site. With his help we have solved it. Thanks a lot
    21 August, 2018
Dear Armin,
thank you very much for reporting a XSS vulnerability.

Best Regards
    20 August, 2018
Provided quick and helpful information which helped us fix the issue. Thank you !
    20 August, 2018
Thanks for finding this XSS vulnerability and notifying us.
    19 August, 2018
It's never fun to hear about a security problem but KhanJanny was polite and prompt with details of the vulnerability, following up on progress and informing me when the issue was resolved. We are very grateful.