A path traversal vulnerability exists in the Mautic Asset API

Overview

A path traversal vulnerability exists in the Mautic Asset API. When creating a local asset through the API, the supplied file path is not restricted to the asset upload directory. An authenticated API user with permission to create assets can register any file that is readable by the web server process as a Mautic asset. When the asset is published, its public download URL serves the contents of that file without authentication. This allows the attacker to read arbitrary files from the server, including Mautic configuration files containing the database password, secret key, and mail (SMTP) credentials, as well as system files and any other file readable by the web server user. Exposed credentials can be used to access the database or other connected services, and anyone with the public asset URL can retrieve the file contents.

Affected

• mautic/core >= 2.3.0 < 5.2.12
• mautic/core >= 6.0.0 < 6.0.10
• mautic/core >= 7.0.0 < 7.2.2

Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.

Workarounds

There are no official workarounds. To mitigate this vulnerability without upgrading, disable API access or restrict asset creation permissions to trusted administrative users. Review existing local assets for file paths outside the asset upload directory.