This feature enables you to send additional notifications to the website owners or admins after the vulnerability is submitted. The total number of additional notification is limited to 10, and to 1 in 24 hours.

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.

Technical details of the vulnerability are currently hidden ("On Hold") to give website operator/owner sufficient time to patch the vulnerability without putting any of its systems or users at risk.
Once patched, vulnerability details can be publicly disclosed by the researcher in at least 30 days since the submission. If for a reason the vulnerability remains unpatched, its details can be disclosed only 90 days.

Scheduled 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.

6 February, 2019 19:46 GMT

For Website Operators and Owners

Please contact the researcher directly to get the vulnerability details. The researcher may also help you fix the vulnerability and advice on how to prevent similar issues:

For remediation best practices, please also refer to OWASP remediation guidelines. More information about coordinate and responsible disclosure on Open Bug Bounty is available here.

DISCLAIMER:
As a non-profit project, Open Bug Bounty never acts as an intermediary between website owners and security researchers.
Our role is strictly limited to independent verification of the reports and proper notification of website owners by all available means.