Skip to content

Commit edb8ccc

Browse files
jrfnldingo-d
authored andcommitted
Add SECURITY.md file (WordPress#2766)
* Add `SECURITY.md` file The other day, Rodrigo and me noticed that WPCS does not have a published security policy (via a `SECURITY.md` file). This commit intends to add such a file, which should help inform security researchers how to disclose any findings they may have. The file is placed in the `.github` directory. This will allow for it to be recognized correctly by GitHub, while not cluttering up the project root directory. Ref: https://docs.github.com/en/code-security/how-tos/report-and-fix-vulnerabilities/configure-vulnerability-reporting/add-security-policy --------- Co-authored-by: jrfnl <jrfnl@users.noreply.github.com> Co-authored-by: Denis Žoljom <dingo-d@users.noreply.github.com>
1 parent 6ab969e commit edb8ccc

1 file changed

Lines changed: 28 additions & 0 deletions

File tree

.github/SECURITY.md

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
# Security Policy
2+
3+
## Supported Versions
4+
5+
The latest minor version of the `3.x` release series is supported for security updates.
6+
7+
## Reporting a Vulnerability
8+
9+
The WordPressCS team takes security bugs seriously. We appreciate your efforts to responsibly disclose your findings, and will make every effort to acknowledge your contributions.
10+
11+
**Please do not report or discuss security vulnerabilities through public GitHub issues, discussions, or pull requests.**
12+
13+
Issues can be reported privately to the maintainers by opening a [Security vulnerability report].
14+
15+
> [!CAUTION]
16+
> Please take note that while the WordPress organisation has a HackerOne program, the WordPress Coding Standards software is not covered by this program.
17+
> Full details of the WordPress Security Policy and the list of covered projects and infrastructure can be found on [HackerOne][WordPress HackerOne].
18+
19+
### Preferences
20+
21+
* Please provide detailed reports with reproducible steps and a clearly defined impact.
22+
* Include the version number of the vulnerable package in your report.
23+
* Fixes are most welcome.
24+
25+
A private PR can be created from the security report to work on and discuss the patch.
26+
27+
[Security vulnerability report]: https://github.com/WordPress/WordPress-Coding-Standards/security/advisories/new
28+
[WordPress HackerOne]: https://hackerone.com/wordpress

0 commit comments

Comments
 (0)