Coordinated and Responsible Vulnerability Disclosure Free Bug Bounty Program 456,207 coordinated disclosures
244,324 fixed vulnerabilities
604 bug bounties with 1224 websites
12,316 researchers, 962 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-951333

Security Researcher geeknik Helped patch 4333 vulnerabilities
Received 6 Coordinated Disclosure badges
Received 8 recommendations
, a holder of 6 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:geeknik Helped patch 4333 vulnerabilities
Received 6 Coordinated Disclosure badges
Received 8 recommendations
Remediation Guide:OWASP XSS Prevention Cheat Sheet
Export Vulnerability Data:Bugzilla Vulnerability Data
JIRA Vulnerability Data [ Configuration ]
Mantis Vulnerability Data
Splunk Vulnerability Data
XML Vulnerability Data [ XSD ]

Vulnerable URL:

Screenshot:  vulnerability

Mirror: Click here to view the mirror

Coordinated Disclosure Timeline

Vulnerability Reported:20 August, 2019 18:41 GMT
Vulnerability Verified:20 August, 2019 18:54 GMT
Website Operator Notified:20 August, 2019 18:54 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 August, 2019 18:54 GMT
Vulnerability Fixed:14 September, 2019 17: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.19 September, 2019 18:41 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:44,511
SSL/TLS Server Test:A+    View Results
Web Server Security Test:C+    View Results
Malware Test:Click here
Domain Health Report:Click here

Latest Submissions

OBB-ID Reported by Status Reported on

  Latest Patched


  Latest Blog Posts

17.10.2019 by geeknik
The "S" in IOT is for Security
16.10.2019 by darknetguy
Best XSS Vectors
01.10.2019 by Renzi25031469
#Security 100%
18.09.2019 by Leon
SSRF | Reading Local Files from DownNotifier server
13.09.2019 by drok3r
Collection of information | Google Hacking and Dorks basic

  Recent Recommendations

    22 October, 2019
Thanks Andre for providing a very professional service. Your report provided all the information that we needed in order to rectify the XSS vulnerability that you have discovered.
    22 October, 2019
Many thanks to Faizan_mark for letting us know of a vulnerability and some suggested solutions.
    22 October, 2019
Thank you Faizan_mark for helping us identify an XSS, really appreciated! The description of the vulnerability was clear and allowed us to make a fix quickly.
    22 October, 2019
Thank you so much for reporting the security issue and bringing this to our attention. We highly appreciate your time and professional skills in helping to make Driver Easy more secure.
We're working on the issue and will update with you when we fix it.
Thanks again for everything.
    21 October, 2019
Thanks very much for the report!
We were sure that everything was proteced, but apparently we missed some special places where the escaping wasn't sufficient.
It is now fixed.