Skip to content

Mautic allows Improper Authorization in Reporting API

High severity GitHub Reviewed Published Feb 25, 2025 in mautic/mautic • Updated Feb 26, 2025

Package

composer mautic/core (Composer)

Affected versions

>= 1.0.1, < 5.2.3

Patched versions

5.2.3

Description

Summary

This advisory addresses an authorization vulnerability in Mautic's HTTP Basic Authentication implementation. This flaw could allow unauthorized access to sensitive report data.

  • Improper Authorization: An authorization flaw exists in Mautic's API Authorization implementation. Any authenticated user, regardless of assigned roles or permissions, can access all reports and their associated data via the API. This bypasses the intended access controls governed by the "Reporting Permissions > View Own" and "Reporting Permissions > View Others" permissions, which should restrict access to non-System Reports.

Mitigation

Please update to Mautic 5.2.3 or later

Workarounds

Disable the API in Mautic. See documentation.

References

https://cwe.mitre.org/data/definitions/285.html
https://docs.mautic.org/en/5.2/configuration/settings.html#api-settings

If you have any questions or comments about this advisory:

Email us at [email protected]

References

@RCheesley RCheesley published to mautic/mautic Feb 25, 2025
Published to the GitHub Advisory Database Feb 26, 2025
Reviewed Feb 26, 2025
Last updated Feb 26, 2025

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

EPSS score

CVE ID

CVE-2024-47053

GHSA ID

GHSA-8xv7-g2q3-fqgc

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.