Report a Vulnerability
Submit, help fixing, get kudos.
Start a Bug Bounty
Run your bounty program for free.
503,513 coordinated disclosures
274,795 fixed vulnerabilities
692 bug bounties with 1,388 websites
14,214 researchers, 1055 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 Cross Site Scripting vulnerability
Open Bug Bounty ID: OBB-235766

Security Researcher SecuNinja Helped patch 3395 vulnerabilities
Received 12 Coordinated Disclosure badges
Received 69 recommendations
, a holder of 12 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]
Discovered and Reported by:SecuNinja Helped patch 3395 vulnerabilities
Received 12 Coordinated Disclosure badges
Received 69 recommendations
Remediation Guide:OWASP XSS Prevention Cheat Sheet

Vulnerable URL:

Mirror: Click here to view the mirror

Coordinated Disclosure Timeline

Vulnerability Reported:12 May, 2017 12:22 GMT
Vulnerability Verified:12 May, 2017 12:24 GMT
Website Operator Notified:12 May, 2017 12:24 GMT
a. Using publicly available security contacts
b. Using Open Bug Bounty notification framework
c. Using security contacts provided by the researcher
Public Report Published
[without any technical details]:
12 May, 2017 12:24 GMT
Vulnerability Fixed:7 August, 2018 16:09 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.11 June, 2017 12:22 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:N/A    
Web Server Security Test:N/A    
Malware Test:Click here
Domain Health Report:Click here

Latest Submissions

OBB-ID Reported by Status Reported on

  Latest Patched


  Latest Blog Posts

10.02.2020 by 0xrocky
Stored XSS on
10.02.2020 by ismailtsdln
SQL Injection Payload List
20.01.2020 by Rando02355205
XSS on "" (Alibaba WAF 405) Bypassed.
16.01.2020 by Open Bug Bounty
Brief Recap of Open Bug Bounty’s Record Growth in 2019
12.01.2020 by JCQ_47
WAF Cloudflare Bypass XSS at

  Recent Recommendations

    16 February, 2020
Thank you Taha for finding and reporting the vulnerability on my website.
    16 February, 2020
Thank you amlnspqr for reporting the xss bug on my website.
    16 February, 2020
Dipu1A found a few vulnerabilities on our website and provided all the details needed to fix them. Thank you!
    13 February, 2020
Incognito007 pointed out a test configuration file on our server that should not have been publicly visible. Thanks!
    13 February, 2020
Identified an XSS issue in our site and provided instruction on how to replicate. As a result we were able to quickly patch and resolve the issue. Thanks!