@@ -15,18 +15,13 @@ If you'd like to be notified of new potential security concerns you can [sign-up
1515If you've found an issue that likely has no impact to existing users (For example, in a development-only branch)
1616feel free to raise it via a standard GitHub bug report issue.
1717
18- If the issue could have a security impact to BookStack instances, please use one of the below
19- methods to report the vulnerability:
20-
21- - Directly contact the lead maintainer [ @ssddanbrown ] ( https://github.com/ssddanbrown ) .
22- - You will need to login to be able to see the email address on the [ GitHub profile page] ( https://github.com/ssddanbrown ) .
23- - Alternatively you can send a DM via Twitter to [ @ssddanbrown ] ( https://twitter.com/ssddanbrown ) .
24- - [ Disclose via huntr.dev] ( https://huntr.dev/bounties/disclose )
25- - Bounties may be available to you through this platform.
26- - Be sure to use ` https://github.com/BookStackApp/BookStack ` as the repository URL.
18+ If the issue could have a security impact to BookStack instances,
19+ please directly contact the lead maintainer [ @ssddanbrown ] ( https://github.com/ssddanbrown ) .
20+ You will need to login to be able to see the email address on the [ GitHub profile page] ( https://github.com/ssddanbrown ) .
21+ Alternatively you can send a DM via Twitter to [ @ssddanbrown ] ( https://twitter.com/ssddanbrown ) .
2722
2823Please be patient while the vulnerability is being reviewed. Deploying the fix to address the vulnerability
2924can often take a little time due to the amount of preparation required, to ensure the vulnerability has
3025been covered, and to create the content required to adequately notify the user-base.
3126
32- Thank you for keeping BookStack instances safe!
27+ Thank you for keeping BookStack instances safe!
0 commit comments