CVE-2022-25770 is a high severity authentication gap in the upgrade script of Mautic, scored 7.8. The upgrade logic was not shielded correctly, and only installs set up a certain way are exposed. The advisory lists patched versions 4.4.13 and 5.1.1, though its text names 4.4.1, so verify before relying on it.
What's affected
Mautic's advisory GHSA-qf6m-6m4g-rmrc, published 18 September 2024, lists the Composer package mautic/core as affected from 1.0.0-beta3 onward, with patched versions 4.4.13 and 5.1.1. It rates the issue High at 7.8, which matches NVD. No workaround is listed.
There is an inconsistency inside the advisory. The patched versions field says 4.4.13 and 5.1.1, but the patches paragraph tells readers to upgrade to 4.4.1 or 5.1.1 or later. A 4.4.1 release would be far older than 4.4.13, so the likely intent is 4.4.13, but I cannot confirm that from the page. Use 4.4.13 or later on the 4.x line, and check the current Mautic release notes.
The advisory also says the vulnerability is mitigated by the fact that Mautic needs to be installed in a certain way to be vulnerable, and does not say what that way is. Do not assume you are safe because your install seems ordinary.
NVD's vector shows a local attack with high complexity, no privileges required and changed scope. The record's kev flag is false.
Weakness class per the record: CWE-306.
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.
Because the advisory does not describe the vulnerable installation style, a good check is whether the upgrade entry point is reachable from outside. Ask your web server or provider whether the upgrade script path is blocked to the public, and check the version either way.
What to do now
- Identify all Mautic instances and their versions.
- Move to 4.4.13 or later on 4.x, or 5.1.1 or later on 5.x, and read the release notes to confirm the fix.
- Ask whoever installed Mautic how it was set up, and restrict access to upgrade related paths to administrators or internal addresses.
- Keep a dependency inventory of the PHP applications you host so that a future advisory like this can be matched quickly.
Why it matters
This is a missing authentication problem for a critical function (CWE-306). An application upgrade process is a powerful function. It changes code and database structure, so anyone who can trigger it without logging in may be able to cause harm.
The advisory's wording about a certain installation style suggests exposure depends on deployment details, which is common for self hosted applications. That makes inventory and configuration review as important as the patch.
The mismatch in version numbers inside the advisory is itself a lesson: take the patched versions field as the machine readable source, then verify against release notes.
Try it yourself
Click through it at your own pace, or open it full screen.
Quick check
Which version number should I trust?
The advisory's patched versions field says 4.4.13 and 5.1.1, but its text says 4.4.1. Use the higher 4.4.13 and confirm in the release notes.
Sources
Last reviewed: 19 October 2026.