Mautic Sessions could be hijacked due to tracking contacts by an auto-incremented ID
Impact
An issue was discovered in Mautic 1.x and 2.x before 2.13.0. It is possible to systematically emulate tracking cookies per contact due to tracking the contact by their auto-incremented ID. Thus, a third party can manipulate the cookie value with +1 to systematically assume being tracked as each contact in Mautic. It is then possible to retrieve information about the contact through forms that have progressive profiling enabled.
Patches
Update to 2.13.0 or later
Workarounds
None
For more information
If you have any questions or comments about this advisory:
- Email us at security@mautic.org
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| Composer package | mautic/core | < 2.13.0 | 2.13.0 |
References
- CVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N- Weakness (CWE)
CWE-200- Platform
- Composer
- Package
mautic/core- Disclosed
- 19.01.2021
- Updated
- 11.10.2026 10:22
Sources and licenses
OSV / GitHub Advisory Database - GHSA-vfxj-qg93-7wwc - CC BY 4.0
Vulnerability history: mautic/core
All published vulnerabilities of this package (Composer package), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 57
- First → latest
- 01.2021 07.2026
- Without a fix
- 1
- Exploited in attacks
- 0
Severity breakdown
- Critical 9
- High 17
- Medium 29
- Low 2
Disclosures per year
- 2021: 16
- 2022: 7
- 2023: 0
- 2024: 13
- 2025: 13
- 2026: 8
-
Mautic Sessions could be hijacked due to tracking contacts by an auto-incremented ID this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.