CVE-2021-27916

Mautic vulnerable to Relative Path Traversal / Arbitrary File Deletion due to GrapesJS builder

Workarounds

No

References

• https://cwe.mitre.org/data/definitions/23.html
• https://cwe.mitre.org/data/definitions/22.html
• https://attack.mitre.org/techniques/T1630/002/

For more information

If you have any questions or comments about this advisory:

Email us at [email protected]

Prior to the patched version, logged in users of Mautic are vulnerable to Relative Path Traversal/Arbitrary File Deletion. Regardless of the level of access the Mautic user had, they could delete files other than those in the media folders such as system files, libraries or other important files.

This vulnerability exists in the implementation of the GrapesJS builder in Mautic.

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

CVE-2021-27916 has a CVSS score of 8.1 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.4.12, 5.0.4); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

Update to 4.4.12 or 5.0.4.

1. What is CVE-2021-27916? CVE-2021-27916 is a high-severity path traversal vulnerability in mautic/core (composer), affecting versions >= 3.3.0, < 4.4.12. It is fixed in 4.4.12, 5.0.4. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. How severe is CVE-2021-27916? CVE-2021-27916 has a CVSS score of 8.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of mautic/core are affected by CVE-2021-27916? mautic/core (composer) versions >= 3.3.0, < 4.4.12 is affected.
4. Is there a fix for CVE-2021-27916? Yes. CVE-2021-27916 is fixed in 4.4.12, 5.0.4. Upgrade to this version or later.
5. Is CVE-2021-27916 exploitable, and should I be worried? Whether CVE-2021-27916 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2021-27916 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2021-27916?
   • Upgrade mautic/core to 4.4.12 or later
   • Upgrade mautic/core to 5.0.4 or later

Other vulnerabilities in mautic/core