You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

33 lines
1.7 KiB

  1. # Security Policy
  2. Wiki.js is built with security in mind. We try our absolute best to deliver secure and robust applications. However, like any software, there can be security bugs, either introduced by an update or by using an attack vector that wasn't considered when designing the software.
  3. If you find such vulnerability, it's important to disclose it in a quick and secure manner to the developers. Follow the instructions below to report a vulnerability.
  4. ## Supported Versions
  5. | Version | Supported |
  6. | ------- | ------------------ |
  7. | 2.x.x | :white_check_mark: |
  8. | 1.x.x | :x: |
  9. ## Reporting a Vulnerability
  10. **DO NOT CREATE A GITHUB ISSUE / DISCUSSION** to report a potential vulnerability / security problem. Instead, choose one of these options:
  11. ### A) Submit a Vulnerability Report *(recommended)*
  12. Fill in the form on https://github.com/requarks/wiki/security/advisories/new
  13. ### B) Send an email
  14. Send an email to security@requarks.io.
  15. Include as much details as possible, such as:
  16. - The version(s) of Wiki.js that are impacted
  17. - How to reproduce the vulnerability (step-by-step, screenshots or a video)
  18. - The platform / environment it occurs on (e.g. OS version, DB type + version, etc.)
  19. - Any potential fixes or reference code you think might be helpful in resolving the issue
  20. - Your GitHub username if you'd like to be included as a collaborator on the private fix branch
  21. The vulnerability will be investigated ASAP. If deemed valid, a draft security advisory will be created on GitHub and you will be included as a collaborator. A fix will be worked on in a private branch to resolves the issue. Once a fix is available, the advisory will be published.