-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Where to report security issues #69
Comments
The
Maybe that needs to be more explicit, though? Where did you expect to find a link to it? Maybe towards the beginning of the document? It doesn't mention anything about reporting plugin vulnerabilities, but maybe that could be added to this paragraph?
Or maybe it'd be better to just have something at the top that says something like:
What does everyone else think? |
The user reporting this wrote the following:
(After giving the pages:)
One answer that was given was: It’s targeted towards the security researcher community. Please feel free to use [email protected] |
That address technically works, but the security team prefers reports to go through HackerOne, since it makes management much much easier. I think it'd be better to work on making the links in your report more visible. Maybe adding a |
This whitepaper give a complete overview of the security around WordPress.org, but it seems to miss the places WHERE to report.
Please consider making links to e.g.
https://make.wordpress.org/core/handbook/testing/reporting-security-vulnerabilities/#where-do-i-report-security-issues
https://developer.wordpress.org/plugins/wordpress-org/plugin-security/reporting-plugin-security-issues/
The text was updated successfully, but these errors were encountered: