GHSA-9fx4-7cmj-47vg
CRITICALMautic has Server-Side Template Injection (SSTI) in Theme Templates
Blast Radius
mautic/core🐘mautic/core🐘mautic/core🐘mautic/coreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Summary
A Server-Side Template Injection (SSTI) vulnerability exists in Mautic's theme engine. The platform renders uploaded Twig templates without a sandbox or strict function restrictions. Authenticated users with permissions to create or upload themes can abuse this to execute arbitrary code.
Impact
An authenticated user with theme upload and creation privileges can bypass boundaries to execute arbitrary system commands on the hosting server (Remote Code Execution) or access restricted system files and configuration settings.
Patched Versions
This security issue has been addressed in the following releases:
- 7.1.2
- 6.0.9
- 5.2.11
For users on Mautic 4.x, this fix is available in:
- 4.4.20 via ELTS
Mautic strongly recommend upgrading to a patched version immediately.
Workarounds
There are no official workarounds. To mitigate this vulnerability without upgrading, restrict theme upload and creation permissions (core:themes:create) to only highly trusted administrators.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | mautic/core | ≥ 1.3.0 | No fix |
| 🐘Packagist | mautic/core | ≥ 5.0.0&&< 5.2.11 | 5.2.11 |
| 🐘Packagist | mautic/core | ≥ 6.0.0&&< 6.0.9 | 6.0.9 |
| 🐘Packagist | mautic/core | ≥ 7.0.0&&< 7.1.2 | 7.1.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mautic/core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
No patched version of mautic/core has shipped for GHSA-9fx4-7cmj-47vg yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-9fx4-7cmj-47vg is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-9fx4-7cmj-47vg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-9fx4-7cmj-47vg in your dependencies?
O3 detects GHSA-9fx4-7cmj-47vg across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.