No technology is perfect, At Fivemroleplay.com, we, believe that working with skilled security researchers across the globe is crucial in identifying weaknesses in any technology. If you believe you’ve found a security issue in our product or service, we encourage you to notify us. We welcome working with you to resolve the issue promptly.
This vulnerability disclosure policy applies to any vulnerabilities you are considering reporting to Fivemroleplay.com found within our scope, websites in our scope will always have a security.txt file that references this policy, additionally, the scope will be listed at the bottom of this page.
Security.txt files can be found in both the Root directory of in-scope domains and the “.well-known” directory of domains.
We recommend reading this vulnerability disclosure policy fully before you report a vulnerability and always acting in compliance with it.
We value those who take the time and effort to report security vulnerabilities according to this policy. However, rewards for disclosures are primarily based on severity.
If you believe you have found a security vulnerability relating to the systems within our scope, please submit a vulnerability report to the address defined in the CONTACT field of the published security.txt file.
In your report please include details of:
- The website, IP or page where the vulnerability can be observed.
- A brief description of the type of vulnerability, for example; “SQL Injection Vulnerability”.
- Steps to reproduce. These should be a benign, non-destructive, proof of concept. This helps to ensure that the report can be triaged quickly and accurately. It also reduces the likelihood of duplicate reports, or malicious exploitation of some vulnerabilities, such as sub-domain takeovers.
- Any additional information that may help with remediation/mitigation.
We’d like to take this opportunity to thank you in advance.Team Fivemroleplay.com
After you have submitted your report, we will respond to your report within 2 working days and aim to triage your report within 3 working days, although in most cases this is much sooner. We’ll also aim to keep you informed of our progress.
Priority for remediation is assessed by looking at the impact, severity and exploit complexity. Vulnerability reports might take some time to triage or address. You are welcome to enquire about the status but should avoid doing so more than once every 7 days. This allows our teams to focus on remediation.
We will notify you when the reported vulnerability is remediated, and you may be invited to confirm that the solution covers the vulnerability adequately.
Once your vulnerability has been resolved, we welcome requests to disclose your report. We’d like to unify our guidance, so please do continue to coordinate the public release with us.
You must NOT:
- Break any applicable law or regulations.
- Access unnecessary, excessive or significant amounts of data.
- Modify data in the Organisation’s systems or services.
- Use high-intensity invasive or destructive scanning tools to find vulnerabilities.
- Attempt or report any form of denial of service, e.g. overwhelming a service with a high volume of requests.
- Disrupt the Organisation’s services or systems.
- Submit reports detailing non-exploitable vulnerabilities, or reports indicating that the services do not fully align with “best practice”, for example missing security headers.
- Submit reports detailing TLS configuration weaknesses, for example “weak” cipher suite support or the presence of TLS1.0 support.
- Communicate any vulnerabilities or associated details other than by means described in the published security.txt.
- Social engineer, ‘phish’ or physically attack the Organisation’s staff or infrastructure.
- Demand financial compensation in order to disclose any vulnerabilities.
- Always comply with data protection rules and must not violate the privacy of any data the Organisation holds. You must not, for example, share, redistribute or fail to properly secure data retrieved from the systems or services.
- Securely delete all data retrieved during your research as soon as it is no longer required or within 1 month of the vulnerability being resolved, whichever occurs first (or as otherwise required by data protection law).
- Report any security risk finding to us no later than 24 hours of discovery.
- Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction of data during security testing;
- Perform research only within the scope set out below;
This policy is designed to be compatible with common vulnerability disclosure good practices. It does not give you permission to act in any manner that is inconsistent with the law, or which might cause the Organisation or partner organisations to be in breach of any legal obligations.
Rewards are primarily* based on severity.
Public Acknowledgements along with a Recommendation and or Swag/Monetary may be awarded to valid reports.
The following domains and all sub-domains are covered within this policy.
*.fivemroleplay.com – Critical
Out of scope
In the interest of the safety of our users, staff, the Internet at large and you as a security researcher, the following test types are excluded from scope:
- Findings from physical testing such as office access (e.g. open doors, tailgating)
- Findings derived primarily from social engineering (e.g. phishing, vishing)
- Findings from applications or systems not listed in the ‘Scope’ section
- UI and UX bugs and spelling mistakes
- Network level Denial of Service (DoS/DDoS) vulnerabilities
- Self-XSS and any XSS where local access is required
Unsure about any aspect of this page? Please contact us