Coordinated and Responsible Vulnerability Disclosure Free Bug Bounty Program 257,178 coordinated disclosures
153,920 fixed vulnerabilities
207,723 websites, 17,218 VIP websites
6,873 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-459702

Security Researcher Spam404 Helped patch 15613 vulnerabilities
Received 8 Coordinated Disclosure badges
Received 68 recommendations
, a holder of 8 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:Spam404 Helped patch 15613 vulnerabilities
Received 8 Coordinated Disclosure badges
Received 68 recommendations
Remediation Guide:OWASP XSS Prevention Cheat Sheet

Vulnerable URL:

Screenshot:  vulnerability

Mirror: Click here to view the mirror

Coordinated Disclosure Timeline

Vulnerability Reported:26 December, 2017 22:52 GMT
Vulnerability Verified:26 December, 2017 22:54 GMT
Website Operator Notified:26 December, 2017 22:54 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]:
26 December, 2017 22:54 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.26 March, 2018 22:52 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
On Hold

  Latest Patched
    Patched on 20.08.2018
    Patched on 20.08.2018
    Patched on 20.08.2018
    Patched on 20.08.2018
    Patched on 20.08.2018
    Patched on 20.08.2018
    Patched on 20.08.2018
    Patched on 19.08.2018
    Patched on 19.08.2018
    Patched on 19.08.2018

  Recent Recommendations

    24 July, 2018
Tarun is very professional and helpful. His research was exemplary and he comes highly recommended. Thanks Tarun!
    23 July, 2018
Siruja provided quick and helpful information which helped us fix the issue. Thank you !
    18 July, 2018
Thanks a lot Adel to help me to improve the security of my website. Your examples were very clear and to the point and your follow-up very thorough. Keep up the good work to make the internet a safer place!
    18 July, 2018
Vielen Dank Armin, dass Sie eine Sicherheitslücke an uns gemeldet haben. Wir nehmen solche Dinge sehr ernst und konnten dank Ihren Hinweisen in Zusammenarbeit mit unserem technischen Dienstleister die Sicherheitslücke beseitigen.
    17 July, 2018
Excellent catch! We thought we fixed all XSS on our site but Siruja found one we missed. Even provided extra detail to test it. Thanks!