Summary
Add a Responsible Security Disclosure comment block to the plugin’s main PHP entry file, immediately below the standard WordPress plugin header comment (Plugin Name:, Plugin URI:, Description:, etc.).
This supports the organization-wide security disclosure contact tracked in the parent issue.
Comment block to add
Place the following block directly after the closing */ of the plugin header comment, before other code:
/**
* * * * * * * * * * * * * * * * * * * * * * *
* *
* Reporting a Security Vulnerability *
* *
* Please disclose any security issues or *
* vulnerabilities to security@caseproof.com *
* *
* * * * * * * * * * * * * * * * * * * * * * *
*/
Email: Use security@caseproof.com as above, or a product-specific alias such as security@{productdomain}.com (e.g. security@memberpress.com) if preferred for this product.
Parent tracking
Tracked as a sub-issue of https://github.com/caseproof/internal-websites-server/issues/251
Summary
Add a Responsible Security Disclosure comment block to the plugin’s main PHP entry file, immediately below the standard WordPress plugin header comment (
Plugin Name:,Plugin URI:,Description:, etc.).This supports the organization-wide security disclosure contact tracked in the parent issue.
Comment block to add
Place the following block directly after the closing
*/of the plugin header comment, before other code:Email: Use
security@caseproof.comas above, or a product-specific alias such assecurity@{productdomain}.com(e.g.security@memberpress.com) if preferred for this product.Parent tracking
Tracked as a sub-issue of https://github.com/caseproof/internal-websites-server/issues/251