Cross Site Request Forgery vulnerability

ID OBB:1083881
Type openbugbounty
Reporter Auntor
Modified 2020-03-05T08:03:00


Open Bug Bounty ID: OBB-1083881

Security Researcher Auntor Helped patch 43 vulnerabilities
Received 3 Coordinated Disclosure badges
Received 3 recommendations
, a holder of 3 badges for responsible and coordinated disclosure, found a security vulnerability affecting 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:|
Open Bug Bounty Program:| Create your bounty program now. It's open and free.
Vulnerable Application:| Custom Code
Vulnerability Type:| CSRF (Cross-Site Request Forgery) / CWE-352
CVSSv3 Score:| 8.8 [CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H]
Disclosure Standard:| Coordinated Disclosure based on ISO 29147 guidelines
Discovered and Reported by:| Auntor Helped patch 43 vulnerabilities
Received 3 Coordinated Disclosure badges
Received 3 recommendations

Remediation Guide:| OWASP CSRF 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:

Research's Comment:

Screenshot Before  vulnerability

Screenshot After  vulnerability

Coordinated Disclosure Timeline

Vulnerability Reported:| 4 February, 2020 08:03 GMT
Vulnerability Verified:| 4 February, 2020 08:46 GMT
Website Operator Notified:| 4 February, 2020 08:46 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]:| 4 February, 2020 08:46 GMT
Vulnerability Fixed:| 4 February, 2020 16:15 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.| 5 March, 2020 08:03 GMT