CVE-2022-25769 is a flaw in the default .htaccess file shipped with Mautic: a filename regex lets unintended PHP files execute. NVD scores it 7.2, High, while the GitHub advisory rates it Moderate. Mautic fixed it in 3.3.5 and 4.2.0, so upgrade to those releases or later.
What's affected
Mautic's GitHub advisory GHSA-mj6m-246h-9w56 lists the Composer package mautic/core as affected before 3.3.5 and before 4.2.0, and gives patched versions of 3.3.5 and 4.2.0. The release post for Mautic 4.2.0, dated 28 February 2022, says that release contains one security fix. No workaround is listed.
Severity and timing differ between sources. NVD scores the flaw 7.2 High with a local attack vector, high privileges, high complexity and changed scope. The Mautic advisory labels it Moderate. The NVD record's published date is 2024-09-18, while the advisory was published in February 2022, so the vulnerability is old and the record is a later entry.
The advisory is short. It says the default .htaccess has restrictions that only allow specific PHP files to be executed in the application root, and that the regular expression in the second FilesMatch block checks only the filename, not the full path. Files with allowed names in other directories therefore pass the check.
The record's kev flag is false.
Weakness class per the record: CWE-1284.
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.
You can also inspect the web server rules. Open the .htaccess file in the web root and read the FilesMatch blocks that control which PHP files run. If the file still has the older rule from before 3.3.5 or 4.2.0, it is the one the advisory describes. Sites that use Nginx rather than Apache rely on their own rules, which are outside this advisory, so check those separately.
What to do now
- Find every Mautic installation, including staging copies and agency hosted sites.
- Upgrade to 3.3.5 if you are on the 3.x line or 4.2.0 or later if you are on 4.x, and then keep up with current releases.
- After upgrading, confirm the new .htaccess is in place, since the fix is in that file and a customized copy may not pick it up.
- Review which PHP files exist outside the web root's intended entry points and remove stray ones.
Why it matters
The weakness is classed as improper handling of a special case in input, CWE-1284 in the record. In practice the rule tested only a filename pattern, so a file with an approved name in a subdirectory slipped through a check meant for files in the application root.
Access control in web server configuration is easy to get slightly wrong. A rule that allows index.php in the root can unintentionally allow index.php anywhere unless it is anchored to the path. Pairing that with any way to place or reuse a PHP file in an unexpected directory is how small configuration mistakes become code execution.
Marketing automation software also holds contact data and credentials for email services, so it is worth treating like any other internet facing application.
Quick check
Is this issue actively exploited?
The record's KEV flag is false and neither source I read reports exploitation. That is not the same as proof that no one has tried.
Sources
- Safeguard Gold entry for CVE-2022-25769
- Mautic advisory GHSA-mj6m-246h-9w56
- Mautic 4.2.0 release post
Last reviewed: 19 October 2026.