cbengine.com Cross Site Scripting vulnerability

2020-07-10T15:48:00
ID OBB:1220902
Type openbugbounty
Reporter devl00p
Modified 2020-10-08T15:48:00

Description

Open Bug Bounty ID: OBB-1220902

Security Researcher devl00p Helped patch 3018 vulnerabilities
Received 10 Coordinated Disclosure badges
Received 15 recommendations
, a holder of 10 badges for responsible and coordinated disclosure, found a security vulnerability affecting cbengine.com website and its users.

Following coordinated and responsible vulnerability disclosure guidelines of the ISO 29147 standard, Open Bug Bounty has:

&nbsp&nbsp&nbsp&nbsp&nbsp&nbspa. verified the vulnerability and confirmed its existence;
&nbsp&nbsp&nbsp&nbsp&nbsp&nbspb. notified the website operator about its existence.

Technical details of the vulnerability are currently hidden ("On Hold") to give website operator/owner sufficient time to patch the vulnerability without putting any of its systems or users at risk. Once patched, vulnerability details can be publicly disclosed by the researcher in at least 30 days since the submission. If for a reason the vulnerability remains unpatched, its details can be disclosed only 90 days.

Affected Website:| cbengine.com
---|---
Open Bug Bounty Program:| Create your bounty program now. It's open and free.
Vulnerable Application:| [hidden until disclosure]
Vulnerability Type:| XSS (Cross Site Scripting) / CWE-79
CVSSv3 Score:| [hidden until disclosure]
Disclosure Standard:| Coordinated Disclosure based on ISO 29147 guidelines
Discovered and Reported by:| devl00p Helped patch 3018 vulnerabilities
Received 10 Coordinated Disclosure badges
Received 15 recommendations

Remediation Guide:| OWASP XSS Prevention Cheat Sheet

Coordinated Disclosure Timeline

Vulnerability Reported:| 10 July, 2020 15:48 GMT
---|---
Vulnerability Verified:| 10 July, 2020 15:59 GMT
Website Operator Notified:| 10 July, 2020 15:59 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]:| 10 July, 2020 15:59 GMT
Scheduled 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.| 8 October, 2020 15:48 GMT
---|---