- Resolve reported security issues in a Security Advisory
- Provide documentation on how to write secure code
- Provide documentation on securing your Mautic instance
- Help the infrastructure team to keep the *.mautic.org infrastructure secure
The Mautic Security Team operates with a limited scope and only directly responds to issues with Mautic core, officially supported plugins and the *.mautic.org network of websites. The team does not directly handle potential vulnerabilities with third party plugins or individual Mautic instances.
Mautic 3 will receive security advisories until 15 December 2021.
Starting with the release of Mautic 3.0, one minor versions at a time receives security advisories, the most recent minor release.
For example, Mautic 3.1 will continue receiving security advisories until the release of Mautic 3.2, and 3.2 will receive security advisories until the release of 3.3.
| Branch | Beta Release | Initial Release | Active Support Until | Security Support Until * |
|---|---|---|---|---|
| 2.16 | 30 Jan 2020 | 13 Feb 2020 | 15 Jun 2020 | 15 Dec 2020 |
| 3.x | 27 Jan 2020 | 15 Jun 2020 | 30 Aug 2021 | 28 Feb 2022 |
| 3.1 | 17 Aug 2020 | 24 Aug 2020 | 23 Nov 2020 | 30 Nov 2020 |
| 3.2 | 23 Nov 2020 | 30 Nov 2020 | 16 Feb 2021 | 22 Feb 2021 |
| 3.3 | 16 Feb 2021 | 22 Feb 2021 | 17 May 2021 | 24 May 2021 |
| 4.x | 16 Feb 2021 | 30 Aug 2021 | 26 Sept 2022 | 27 Feb 2023 |
| 4.0 | 25 May 2021 | 30 Aug 2021 | 29 Nov 2021 | 29 Nov 2021 |
| 4.1 | N/A | 29 Nov 2021 | 21 Feb 2021 | 21 Feb 2021 |
| 4.2 | 17 Feb 2022 | 28 Feb 2021 | 23 May 2022 | 23 May 2022 |
| 4.3 | 17 May 2022 | 23 May 2022 | 27 Jun 2021 | 27 Jun 2022 |
| 4.4 | 27 Jun 2022 | 27 Jun 2022 | 26 Sept 2022 | 26 Sept 2022 |
* = Security Support for 2.16 will only be provided for Mautic itself, not for core dependencies that are EOL like Symfony 2.8.
Security advisories are only made for issues affecting stable releases in the supported major version branches. That means there will be no security advisories for development releases (-dev), alphas, betas or release candidates.
If you discover or learn about a potential error, weakness, or threat that can compromise the security of Mautic and is covered by the Security Advisory Policy, we ask you to keep it confidential and submit your concern to the Mautic security team.
To make your report please submit it via https://huntr.dev.
Do not post it in Github, the forums, or or discuss it in Slack.
Read more: How to report a security issue with Mautic
The Mautic Security Team are responsible for triaging incoming security issues relating to Mautic core and officially supported plugins, and for releasing fixes in a timely manner.
Read more: How are security issues triaged and resolved by the Mautic Security Team?
The Security Team coordinates security announcements in release cycles and evaluates whether security issues are ready for release several days in advance.
The team may deem it necessary to make an out-of-sequence release, in which case at least two weeks’ notice will be provided to ensure that Mautic users are made aware of a security release being made on an unscheduled basis.
Read more: Security fix announcements and releases
A security advisory is a public announcement managed by the Mautic Security Team which informs Mautic users about a reported security problem in Mautic core or an officially supported plugin and the steps Mautic users should take to address it. (Usually this involves updating to a new release of the code that fixes the security problem.)
Read more: Mautic Security Advisory Policy
The security team follows a Coordinated Disclosure policy: we keep issues private until there is a fix. Public announcements are made when the threat has been addressed and a secure version is available.
When reporting a security issue, observe the same policy. Do not share your knowledge of security issues with others.
As membership in the team gives the individual access to potentially destructive information, membership is limited to people who have a proven track record in the Mautic community.
Team members are expected to work at least a few hours every month. Exceptions to that can be made for short periods to accommodate other priorities, but people who can't maintain some level of involvement will be asked to reconsider their membership on the team.
Read more: How do I join the Mautic Security Team?
You can meet the Mautic Security Team on the page below.
Read more: Meet the Mautic Security Team
Resources and guidance from the Drupal, Joomla and Mozilla projects have been drawn from to create these documents and develop our processes/workflows.
Always report the issue to the team and let them make the decision on whether to handle it in public or private.