Skip to content

Mautic Sensitive Data Exposure due to inadequate user permission settings

High severity GitHub Reviewed Published Apr 11, 2024 in mautic/mautic • Updated Sep 18, 2024

Package

composer mautic/core (Composer)

Affected versions

>= 1.0.2, < 4.4.12
>= 5.0.0-alpha, < 5.0.4

Patched versions

4.4.12
5.0.4

Description

Impact

Prior to the patched version, logged in users of Mautic are able to access areas of the application that they should be prevented from accessing.

Users could potentially access sensitive data such as names and surnames, company names and stage names.

Patches

Update to 4.4.12 and 5.0.4

Workarounds

No

References

https://owasp.org/www-project-top-ten/2017/A3_2017-Sensitive_Data_Exposure

References

@RCheesley RCheesley published to mautic/mautic Apr 11, 2024
Published to the GitHub Advisory Database Apr 12, 2024
Reviewed Apr 12, 2024
Published by the National Vulnerability Database Sep 18, 2024
Last updated Sep 18, 2024

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
Unchanged
Confidentiality
High
Integrity
Low
Availability
High

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:U/C:H/I:L/A:H

EPSS score

0.052%
(22nd percentile)

Weaknesses

CVE ID

CVE-2022-25776

GHSA ID

GHSA-qjx3-2g35-6hv8

Source code

Credits

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