Coordinated and Responsible Vulnerability Disclosure Free Bug Bounty Program 307,880 coordinated disclosures
179,529 fixed vulnerabilities
337 bug bounties with 733 websites
8,475 researchers

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

Security Researcher Dshellnoi_Unix, 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:Open Redirect / CWE-601
CVSSv3 Score:3.4 [CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:N/I:L/A:N]
Discovered and Reported by:Dshellnoi_Unix
Remediation Guide:OWASP Open Redirect Cheat Sheet

Vulnerable URL:

Mirror: Click here to view the mirror

Coordinated Disclosure Timeline

Vulnerability Reported:17 September, 2014 04:11 GMT
Vulnerability Verified:18 September, 2014 10:31 GMT
Website Operator Notified:18 September, 2014 10:31 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]:
18 September, 2014 10:31 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.17 September, 2014 04:11 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:824
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
    Patched on 22.01.2019
    Patched on 22.01.2019
    Patched on 22.01.2019
    Patched on 22.01.2019
    Patched on 22.01.2019
    Patched on 22.01.2019
    Patched on 22.01.2019
    Patched on 22.01.2019
    Patched on 22.01.2019
    Patched on 22.01.2019

  Recent Recommendations

    22 January, 2019
Following Felipe's disclosure, we have now fixed the Reflected Cross-Site Scripting web vulnerability you discovered in our "" web-application. We'd like to thank Felipe for his prompt and professional disclosure.
    22 January, 2019
Armin found an XSS bug in our product and was nice and supportive to help us in dealing with the vulnerability. We were able to release an update just a few hours after discovery.

Thank you so much Armin for making the web a better place!
    22 January, 2019
Found a xss issue, quickly emailed with the affected pages and links to aid resolving. Many thanks
    21 January, 2019
Guten Tag Armin

Besten Dank für Ihre Mail und die Dokumentation der eruierten XXS-Schwachstelle. Wir sind in einem laufenden Prozess daran Schwachstellen, wie die von Ihnen Identifizierte, zu eruieren und zu beheben.
Die Sensibilisierung der Entwickler zur Verhinderung von Sicherheitslücken bedarf offenbar weiterer Schritte, für Ihr professionelles Vorgehen und den Hinweis möchten wir uns bedanken.

    21 January, 2019
Awesome recommendations to help the site have less vulnerabilities. Thank you again for your support!