Skip to content

Cross-site Scripting vulnerability in Mautic's tracking pixel functionality

Critical severity GitHub Reviewed Published May 23, 2022 in mautic/mautic • Updated May 10, 2023

Package

composer mautic/core (Composer)

Affected versions

< 4.3.0

Patched versions

4.3.0

Description

Impact

Mautic allows you to track open rates by using tracking pixels.
The tracking information is stored together with extra metadata of the tracking request.

The output isn't sufficiently filtered when showing the metadata of the tracking information, which may lead to a vulnerable situation.

Patches

Please upgrade to 4.3.0

Workarounds

None.

References

  • Internally tracked under MST-38

For more information

If you have any questions or comments about this advisory:

References

@escopecz escopecz published to mautic/mautic May 23, 2022
Published to the GitHub Advisory Database May 25, 2022
Reviewed May 25, 2022
Published by the National Vulnerability Database Jun 20, 2022
Last updated May 10, 2023

Severity

Critical

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
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
Low

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:N/UI:R/S:C/C:H/I:H/A:L

EPSS score

0.354%
(72nd percentile)

Weaknesses

CVE ID

CVE-2022-25772

GHSA ID

GHSA-pjpc-87mp-4332

Source code

Credits

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