CVE-2026-9558: Critical Mautic SSTI
Critical CVSS (9.9) reachable over network.
TL;DR - CVE-2026-9558 is a critical server-side template injection flaw in Mautic’s theme engine, rated CVSS 9.9. - Authenticated users who can create or upload themes may execute code or read restricted files. - Upgrade to Mautic 7.1.2 or later, or 4.4.20 for the applicable 4.x ELTS branch. - No confirmed in-the-wild exploitation was identified in the supplied records.
Vulnerability at a Glance
| Field | Details |
|---|---|
| CVE ID | CVE-2026-9558 |
| Product | Mautic theme engine |
| CVSS | 9.9 Critical |
| CVSS vector | Not provided in the retrieved NVD record |
| Attack vector | Network-accessible authenticated application interface |
| Authentication | Required |
| Privileges required | Permission to create or upload themes |
| User interaction | Not separately documented in the retrieved record |
| Patch available | Yes |
| Fixed versions | Mautic 7.1.2 and later; Mautic 4.4.20 and later through applicable ELTS |
| CISA KEV status | Not listed |
| Public advisory | GHSA-9fx4-7cmj-47vg |
CVE-2026-9558 is a Mautic vulnerability involving server-side template injection (SSTI). The affected functionality processes uploaded or administrator-created Twig templates. Because the templates are not rendered with sufficient sandboxing or sufficiently strict function restrictions, template logic may reach operations that should not be available to user-controlled content.
The required account is not necessarily a full operating-system administrator. An authenticated Mautic user with theme-management permissions may be able to turn template rendering into server-side code execution, file disclosure, or access to application configuration and secrets.
Analyst’s Take: Patch this before relying on permission restrictions. Theme-management access is a meaningful prerequisite, but the documented impact includes code execution and access to configuration data, so reducing the eligible user group does not remove the underlying exposure.
What Is This Vulnerability?
The root cause is unsafe handling of attacker-controlled Twig templates in Mautic’s theme engine. A theme is normally an application presentation component, but the engine evaluates Twig expressions and functions while rendering it. In affected versions, the rendering path does not apply adequate sandboxing or function restrictions to prevent template content from reaching sensitive server-side capabilities.
The practical attack sequence is:
- An authenticated user obtains permission to create or upload a theme.
- The user supplies a malicious Twig template or modifies an existing theme.
- Mautic renders the template through the vulnerable theme engine.
- Template-controlled functionality is invoked during rendering.
- The attacker may execute code, read local files, access configuration data, or otherwise compromise the host and application.
The available research material does not provide a weaponized payload, function-by-function exploit chain, or public proof of concept. Defenders should nevertheless treat the issue as a potential remote-code-execution condition because the documented impact includes arbitrary code execution on the Mautic host.
The impact can extend beyond the Mautic process. Configuration files and environment settings may contain database credentials, API tokens, SMTP credentials, encryption keys, or other secrets. If the Mautic service account has excessive filesystem or operating-system privileges, successful exploitation may also permit lateral movement or broader host compromise.
For background on broader security governance and prioritization, see our NIST Cybersecurity Framework glossary.
Who Is Affected?
The vendor advisory identifies Mautic versions 1.3.0 and earlier as affected. The vulnerable component is the theme template and rendering functionality, and exploitation requires an authenticated account with permission to create or upload themes.
The supplied advisory material also identifies a remediation path for later supported or extended-support branches. Mautic organizations using the 4.x ELTS branch should upgrade to Mautic 4.4.20 or later. Organizations able to move to the current major branch should upgrade to Mautic 7.1.2 or later.
| Mautic version or branch | Status | Required action |
|---|---|---|
| 1.3.0 and earlier | Affected | Upgrade; do not rely only on access restrictions |
| 4.x ELTS before 4.4.20 | Treat as requiring remediation | Upgrade to 4.4.20 or later through applicable ELTS |
| 4.4.20 and later | Listed remediation version | Confirm the release is appropriate for the deployment and support arrangement |
| 7.1.2 and later | Listed remediation version | Upgrade to 7.1.2 or later |
The available material does not establish additional affected version ranges beyond the documented 1.3.0 and earlier range, nor does it provide a complete compatibility matrix for every Mautic release line. Administrators should verify the installed version and consult the vendor advisory before selecting a target release. Without a definitive branch-specific statement, treat an instance with vulnerable theme-rendering behavior as exposed until the vendor-provided fixed release is installed.
CVSS Score Breakdown
CVE-2026-9558 has a reported base score of 9.9, classified as Critical. The retrieved NVD data does not include the CVSS vector string. Individual metric values such as exact attack complexity, confidentiality impact, integrity impact, and availability impact therefore cannot be stated reliably.
The score is consistent with a vulnerability that can produce severe consequences after an authenticated user reaches the affected feature. Server-side code execution may allow an attacker to modify application data, access restricted files, steal credentials, alter content, disrupt availability, or use the Mautic host as a platform for further attacks.
Authentication and theme-management permissions are meaningful prerequisites, but they do not make the issue low risk. Many Mautic deployments have multiple administrators, marketing users, developers, contractors, or integrations with elevated application roles. Compromise of any such account, or misuse of a legitimate account, could provide the initial access required by the vulnerability.
Because the vector is unavailable in the retrieved record, defenders should not infer that network reachability or privilege requirements eliminate urgency. Use the stated 9.9 score for prioritization, then refine risk using local facts: internet exposure, number of users allowed to manage themes, service-account privileges, secrets accessible to Mautic, and evidence of suspicious theme changes.
Exploitation Status
No confirmed in-the-wild exploitation was identified in the retrieved NVD, CISA Known Exploited Vulnerabilities, or vendor advisory data. CVE-2026-9558 is not listed in the CISA KEV catalog. There is therefore no CISA KEV date-added value, due date, required action, or ransomware-campaign flag for this CVE in the supplied data.
A public GitHub Security Advisory exists: GHSA-9fx4-7cmj-47vg. The available records do not identify a standalone public exploit repository or a published proof of concept. The practical exploitation path is understood at a high level, but that is not the same as confirmed weaponized exploitation.
The operational conclusion is: no confirmed active exploitation and no known public PoC were identified in the supplied sources, but the vulnerability is technically exploitable by an appropriately authorized user and should be patched urgently. Absence from KEV or absence of a public PoC does not prove that exploitation has not occurred. Organizations should investigate local evidence rather than treating the current intelligence status as assurance.
How to Detect It
Detection should focus on the activity required to exploit the issue: successful authentication by an account with theme-management privileges, theme creation or upload, changes to Twig files, and unusual requests or process activity immediately after a theme is rendered. Correlate Mautic logs, reverse-proxy logs, web-server logs, filesystem monitoring, and endpoint telemetry by user, source address, timestamp, and theme identifier.
Start by identifying all accounts that can create, edit, or upload themes. Review historical use of those permissions and compare recent changes with approved maintenance activity. Pay particular attention to new or modified .twig files containing unexpected function calls, file access behavior, command-execution behavior, encoded content, or template logic unrelated to the theme’s presentation purpose.
Technical Notes: Detection Queries and Log Patterns
The exact Mautic log format depends on the deployment and logging configuration. The following examples are starting points, not vendor-specific signatures. Adjust paths, field names, and event names to match the installation.
Search web and reverse-proxy logs for theme-management routes and suspicious post-authentication activity:
grep -RniE \
'theme|upload|template|twig' \
/var/log/nginx /var/log/apache2 /var/log/mautic 2>/dev/null
A generic Sigma-style pattern for triage can be adapted to the organization’s log schema:
title: Mautic Theme Management Activity
logsource:
category: webserver
detection:
selection:
url|contains:
- "/theme"
- "/themes"
- "upload"
http_method:
- "POST"
- "PUT"
condition: selection
level: medium
Correlate those events with process execution from the Mautic service account. A potentially serious pattern is a web-server or PHP process spawning a shell, interpreter, downloader, or unexpected utility:
parent process: php-fpm|apache2|httpd
child process: sh|bash|dash|python|perl|curl|wget|nc
user: mautic|www-data|apache
This pattern is not proof of exploitation; legitimate maintenance jobs may produce similar events. It becomes higher priority when it follows a theme upload or modification, originates from an unusual administrator account, or accesses configuration files and credential stores.
Also inspect the Mautic application directory and theme locations for recently changed files:
find /path/to/mautic -type f \
\( -name '*.twig' -o -path '*/themes/*' \) \
-mtime -14 -printf '%TY-%Tm-%Td %TH:%TM:%TS %u %p\n' \
2>/dev/null | sort
If suspicious activity is found, preserve logs and affected files before cleanup. Review database credentials, API keys, SMTP passwords, OAuth secrets, and other values accessible to the Mautic process. A successful template injection may expose secrets even if no command execution is observed.
Mitigation and Patching
The primary remediation is to upgrade to a fixed release. For the current remediation path, upgrade to Mautic 7.1.2 or later. Organizations that must remain on the Mautic 4.x ELTS branch should upgrade to Mautic 4.4.20 or later, subject to the applicable ELTS support and compatibility requirements.
Before upgrading, create a tested backup of the database and application files, record the installed version, and review custom themes for compatibility. After upgrading, confirm the running version from the application’s administration interface or the deployment’s package and release metadata. Do not assume that updating a separate PHP dependency or disabling a web route fixes the issue unless the vendor’s advisory explicitly documents that workaround.
A deployment-specific upgrade command cannot be stated safely without knowing whether Mautic was installed with Composer, a distribution package, a container image, or another deployment method. Use the command that matches the installation method and validate the target release in a staging environment first.
Technical Notes: Upgrade and Workaround Examples
For a Composer-managed deployment, a release-targeted workflow may look like this, but administrators must adapt it to the project’s supported PHP and dependency constraints:
cd /var/www/mautic
# Preserve the current state before changing dependencies.
composer show mautic/core
cp .env .env.pre-cve-2026-9558
php bin/console cache:clear
# Select a vendor-supported fixed release using the deployment's
# documented Composer constraints.
composer require mautic/core:^7.1.2 --with-all-dependencies
php bin/console doctrine:migrations:migrate --no-interaction
php bin/console cache:clear
Do not run that example unchanged against a Mautic 4.x ELTS deployment. For that branch, use the vendor-supported update procedure to reach 4.4.20 or later and verify the resulting dependency set. Containerized deployments should update the image tag to a vendor-supported image containing Mautic 7.1.2 or later, or the corresponding 4.4.20 ELTS release, then redeploy using the normal controlled rollout process.
If immediate patching is impossible, apply temporary containment:
- Remove theme creation and upload permissions from all users except a small, trusted administrator group.
- Disable or restrict theme-management routes at the application or reverse-proxy layer where operationally feasible.
- Prevent untrusted users from editing existing themes.
- Review and remove unapproved themes, while preserving copies for investigation.
- Run Mautic under a minimally privileged service account with restricted filesystem access.
- Restrict outbound network access from the Mautic host to reduce post-exploitation options.
- Rotate secrets if suspicious theme activity or code execution is suspected.
Permission restrictions are a workaround, not a patch. They reduce the number of accounts that can reach the vulnerable functionality but do not remove the unsafe rendering behavior. Treat affected, internet-accessible instances as high priority and accelerate the upgrade.
For related application-security tooling guidance, see our comparison of the best SAST tools for developers in 2026.
References
-
NVD: CVE-2026-9558
NVD record containing the reported vulnerability description and CVSS 9.9 score. The retrieved record did not provide a CVSS vector string. -
Mautic GitHub Security Advisory: GHSA-9fx4-7cmj-47vg
Vendor-associated advisory identifying affected versions and remediation releases. -
CISA Known Exploited Vulnerabilities Catalog
CVE-2026-9558 was not listed in the supplied KEV lookup.
The NVD publication date in the supplied record is 2026-05-29, with the record last modified on 2026-07-21. Security teams should recheck the advisory and NVD record during remediation because exploitation status, affected-version data, and vendor guidance may change.
This article may contain affiliate links. We earn a commission on qualifying purchases at no extra cost to you.