strong-testimonials
Last commit date
.claude
1 month ago
admin
1 day ago
assets
1 month ago
includes
1 day ago
languages
1 year ago
templates
1 week ago
SECURITY.md
1 year ago
changelog.txt
1 day ago
class-strong-testimonials.php
1 month ago
license.txt
1 year ago
readme.txt
5 hours ago
strong-testimonials.php
5 hours ago
uninstall.php
1 year ago
webpack.config.react-apps.js
1 month ago
wpml-config.xml
1 year ago
SECURITY.md
25 lines
| 1 | # Security Policy |
| 2 | |
| 3 | ## Reporting a Vulnerability |
| 4 | |
| 5 | |
| 6 | ### The rules |
| 7 | - Please provide detailed reports with reproducible steps. |
| 8 | - Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact. |
| 9 | - When testing has an overlap with systems or services not owned by you, the tester, make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of that service. Only interact with accounts you own or with the explicit permission of the account holder. |
| 10 | |
| 11 | ### Disclosure Policy |
| 12 | Please do not discuss any vulnerabilities (even resolved ones) without express consent. |
| 13 | |
| 14 | ### Submit your report |
| 15 | When you've found a security issue that abides by the rules and scope of this project, please submit the report to us via heyyy@wpchill.com. In your mail, make sure to include: |
| 16 | |
| 17 | - the impact of the issue; |
| 18 | - a detailed guide on how to reproduce the issue; |
| 19 | |
| 20 | ### After your submission |
| 21 | We will make a best effort to meet the following response targets for security reports: |
| 22 | |
| 23 | - Time to first response (from report submit) - 5 business days |
| 24 | - Time to triage (from report submit) - 15 business days |
| 25 |