noexcusesperformance.com Cross Site Scripting vulnerability

2020-03-11T12:46:00
ID OBB:1115996
Type openbugbounty
Reporter geeknik
Modified 2020-06-09T12:46:00

Description

Open Bug Bounty ID: OBB-1115996

Security Researcher geeknik Helped patch 8908 vulnerabilities
Received 8 Coordinated Disclosure badges
Received 21 recommendations
, a holder of 8 badges for responsible and coordinated disclosure, found a security vulnerability affecting noexcusesperformance.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:| noexcusesperformance.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:| geeknik Helped patch 8908 vulnerabilities
Received 8 Coordinated Disclosure badges
Received 21 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: noexcusesperformance.com  vulnerability

Mirror: Click here to view the mirror

Coordinated Disclosure Timeline

Vulnerability Reported:| 11 March, 2020 12:46 GMT
---|---
Vulnerability Verified:| 11 March, 2020 12:55 GMT
Website Operator Notified:| 11 March, 2020 12:55 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]:| 11 March, 2020 12:55 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.| 9 June, 2020 12:46 GMT
---|---