rybkachess.com Cross Site Scripting vulnerability

2019-07-09T10:08:00
ID OBB:882413
Type openbugbounty
Reporter amlnspqr
Modified 2019-10-07T10:08:00

Description

Open Bug Bounty ID: OBB-882413

Security Researcher amlnspqr Helped patch 1852 vulnerabilities
Received 7 Coordinated Disclosure badges
Received 36 recommendations
, a holder of 7 badges for responsible and coordinated disclosure, found a security vulnerability affecting rybkachess.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.

Affected Website:| rybkachess.com
---|---
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:| amlnspqr Helped patch 1852 vulnerabilities
Received 7 Coordinated Disclosure badges
Received 36 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: rybkachess.com  vulnerability

Mirror: Click here to view the mirror

Coordinated Disclosure Timeline

Vulnerability Reported:| 9 July, 2019 10:08 GMT
---|---
Vulnerability Verified:| 9 July, 2019 10:22 GMT
Website Operator Notified:| 9 July, 2019 10:22 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]:| 9 July, 2019 10:22 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.| 7 October, 2019 10:08 GMT
---|---