Only the latest 2.x stable release is fully supported and receives security and bug fixes.
The legacy 1.3.x series is no longer actively supported, and only gets fixes for critical issues and vulnerabilities.
Earlier releases (1.2.x and older) are not supported anymore.
If you discover a security issue (or what you think could be one), please open a new issue in our bug tracker following the guidelines below. Please note that you must sign up and be logged in with your mantisbt.org account to report issues.
These are public channels which would effectively disclose the security issue.
One of the core team members will review, reply and ask for additional information as required. We will then discuss the means of fixing the vulnerability and agree on a calendar for disclosure. Generally this discussion takes place within the issue itself, but in some cases it may happen privately, e.g. by e-mail.
- Set Category to security ①
- Make sure that View Status is set to Private ①; this will hide your report from the general public, and only MantisBT developers will have access to it.
- Set the Product Version as appropriate; if necessary (e.g. when multiple versions are affected), include additional information in the Description field or in a bugnote.
- Provide a descriptive Summary and clear Description of the issue
- Do not forget detailed Steps To Reproduce to facilitate our work in analyzing and fixing the problem
- If you already have a patch for the issue, please attach it to the issue
① These fields will be preset if you use the provided link.
To ensure a comprehensive, consistent and detailed declaration of the issue, we generally prefer requesting CVE IDs ourselves. The request is usually sent to MITRE after we have analyzed the issue and confirmed the vulnerability.
Should you wish to be credited for the finding, kindly indicate it under Additional Information or in a bug note. Your name/e-mail/company will be included in the CVE report as specified.
In case you have already obtained a CVE, do not forget to reference its ID in the bug report
For further information, please refer to the MantisBT Wiki.