CVE-2022-25775 is a medium severity SQL injection in the Reports bundle of Mautic, scored 6.6 by NVD and rated Moderate by the project. A logged-in user could read and alter data. Upgrade to Mautic 4.4.12 or 5.0.4, or later releases.
What's affected
Mautic's advisory GHSA-jj6w-2cqg-7p94, published 11 April 2024, lists the Composer package mautic/core as affected from version 2.14.1 onward, and gives patched versions 4.4.12 and 5.0.4. It rates the issue Moderate at 6.6, which matches NVD's 6.6 Medium. No workaround is listed.
The advisory says that prior to the patched version, logged in users are vulnerable to SQL injection in the Reports bundle. The user could retrieve and alter data, including sensitive data and logins, and depending on database permissions could manipulate the file system.
The attack needs a logged in account and, per NVD, high privileges, which narrows the audience. In many Mautic installs, though, several marketing staff and agency users have report access. The vector reflects high complexity and high impact on confidentiality, integrity and availability.
The record's kev flag is false and I did not find reports of exploitation.
Weakness class per the record: CWE-89.
How to check if you're exposed
Work out which Mautic version you run. The admin interface shows it in the About dialog, and for installs managed with Composer the advisory's package name is mautic/core:
composer show mautic/core
Compare the result with the patched versions above. If you run a hosted or managed Mautic, ask your provider which release they run.
Then review who can create or edit reports. If you cannot upgrade immediately, tighten the role permissions for the Reports bundle to the smallest group possible.
What to do now
- Find Mautic installs and their versions, including agency managed ones.
- Upgrade to 4.4.12 or later on 4.x, or 5.0.4 or later on 5.x.
- Review user roles and remove report editing rights from people who do not need them.
- Check the database account Mautic uses and remove privileges it does not need, such as file operations, since the advisory notes file system impact depends on them.
Why it matters
SQL injection (CWE-89) happens when user controlled input becomes part of a database query without proper separation of code and data. In reports, which often build queries from user selected fields and filters, that risk is a recurring theme.
The advisory mentions that file system manipulation depends on database permissions. That is the practical defense in depth lesson: a database account that can only touch its own tables cannot be used to write files, even if a query is subverted.
Reachability matters here. A flaw behind a login with high privileges is less urgent than an anonymous one, but it still deserves a patch window, since credentials leak and users change roles.
Try it yourself
Click through it at your own pace, or open it full screen.
Quick check
Does an attacker need to log in?
Yes. The advisory says logged in users of Mautic are the ones vulnerable, and NVD records high privileges required.
Sources
Last reviewed: 19 October 2026.