Lucene search
Gh05tPTOBB:984293HistoryOct 01, 2019 - 11:45 a.m.
401location.com Cross Site Scripting vulnerability
2019-10-0111:45:00
Gh05tPT
www.openbugbounty.org
7
Open Bug Bounty ID: OBB-984293
Security Researcher Gh05tPT Helped patch 6892 vulnerabilities
Received 10 Coordinated Disclosure badges
Received 48 recommendations , a holder of 10 badges for responsible and coordinated disclosure, found a security vulnerability affecting401location.com 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.
| Affected Website: | 401location.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: | **Gh05tPT Helped patch 6892 vulnerabilities |
| Received 10 Coordinated Disclosure badges | |
| Received 48 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:
HTTP POST data:
Research’s Comment:
Screenshot: 
Mirror: Click here to view the mirror
Coordinated Disclosure Timeline
| Vulnerability Reported: | 1 October, 2019 11:45 GMT |
|---|---|
| Vulnerability Verified: | 1 October, 2019 11:52 GMT |
| Website Operator Notified: | 1 October, 2019 11:52 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]: | 1 October, 2019 11:52 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. |
30 December, 2019 11:45 GMT |
| — | — |