raxco.com Cross Site Scripting vulnerability

ID OBB:1136816
Type openbugbounty
Reporter Teamhash
Modified 2020-07-08T09:33:00


Open Bug Bounty ID: OBB-1136816

Security Researcher Teamhash Helped patch 330 vulnerabilities
Received 3 Coordinated Disclosure badges
Received 2 recommendations
, a holder of 3 badges for responsible and coordinated disclosure, found a security vulnerability affecting raxco.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:| raxco.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:| Teamhash Helped patch 330 vulnerabilities
Received 3 Coordinated Disclosure badges
Received 2 recommendations

Remediation Guide:| OWASP XSS Prevention Cheat Sheet

Coordinated Disclosure Timeline

Vulnerability Reported:| 9 April, 2020 09:33 GMT
Vulnerability Verified:| 13 April, 2020 07:41 GMT
Website Operator Notified:| 13 April, 2020 07:41 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]:| 13 April, 2020 07:41 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 July, 2020 09:33 GMT