Lucene search
4N_CURZEOBB:1117156HistoryMar 12, 2020 - 5:56 p.m.
witneygazette.co.uk Cross Site Scripting vulnerability
2020-03-1217:56:00
4N_CURZE
www.openbugbounty.org
4
Open Bug Bounty ID: OBB-1117156
Security Researcher 4N_CURZE Helped patch 1507 vulnerabilities
Received 7 Coordinated Disclosure badges
Received 13 recommendations , a holder of 7 badges for responsible and coordinated disclosure, found a security vulnerability affectingwitneygazette.co.uk 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: | witneygazette.co.uk |
|---|---|
| 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: | **4N_CURZE Helped patch 1507 vulnerabilities |
| Received 7 Coordinated Disclosure badges | |
| Received 13 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:
Cookies:
Research’s Comment:
Mirror: Click here to view the mirror
Coordinated Disclosure Timeline
| Vulnerability Reported: | 12 March, 2020 17:56 GMT |
|---|---|
| Vulnerability Verified: | 13 March, 2020 16:07 GMT |
| Website Operator Notified: | 13 March, 2020 16:07 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 March, 2020 16:07 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. |
10 June, 2020 17:56 GMT |
| — | — |