/

CVE-2026-69118

Severity:

HIGH RISK

(8.8)

Server-Side Template Injection (CWE-1336) in Cachet

CVE-2026-69118

Deferred

Vulnerability type

Category:

Server-Side Template Injection

CWE:

CWE-863, CWE-1336

Impact:

Remote Code Execution

Severity:

HIGH RISK

(8.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Cachet contains a server-side template injection vulnerability in incident template rendering that can allow authenticated users to execute arbitrary PHP code. When a malicious template is processed during incident creation, attacker-controlled directives or filters may execute system commands as the web server process.

Affected context

The vulnerability may occur in Cachet deployments where authenticated users can create or modify incident templates and those templates are later rendered by a server-side template engine. Risk depends on the application's authorization configuration, template handling workflow, and the privileges available to the web server process.

Exploit preconditions

  • Attack surface: Incident template creation and server-side rendering
  • Required access: An authenticated account with permission to create or modify incident templates
  • Trigger point: Rendering a malicious template when an incident is created or processed
  • Why exploitation is possible: Template content is interpreted as executable template logic rather than being treated solely as untrusted data, potentially allowing server-side code execution

Why this happens

The underlying issue is insufficient separation between trusted template logic and user-controlled template content. When attacker-controlled directives, expressions, or filters are evaluated by a server-side template engine, the template may access functionality beyond safe presentation rendering.

This maps primarily to CWE-1336: Improper Neutralization of Special Elements Used in a Template Engine, commonly known as server-side template injection. The associated authorization weakness, CWE-863, reflects the importance of ensuring that only appropriately trusted users can access template-management functionality.

Potential impact

  • An attacker may execute arbitrary PHP code as the web server process.
  • The application and its hosted data could be compromised.
  • Credentials, configuration secrets, or database contents could be exposed.
  • Attackers could modify incidents, deface the service, or disrupt availability.
  • The compromised process could be used for further movement within the environment, depending on its privileges.

General mitigation guidance

Mitigation generally focuses on preventing untrusted users from defining executable templates and reducing the capabilities available during rendering.

Common defensive patterns include:

  • Treating user-supplied content as data and rendering it through context-aware escaping rather than evaluating it as template logic.
  • Using restricted, sandboxed template environments with disabled code execution, filesystem access, and unsafe filters.
  • Applying strict allowlists for permitted template fields, directives, functions, and filters.
  • Separating template administration from ordinary incident-management permissions and enforcing least privilege.
  • Validating and storing templates through controlled workflows with appropriate review and audit logging.
  • Running the web process with minimal filesystem, operating-system, and database privileges.
  • Avoiding the exposure of secrets and privileged service interfaces to the rendering process.

How teams detect issues like this

Detection approaches may include:

  • Static analysis for dynamic template evaluation, unsafe expression handling, and template compilation of user-controlled values.
  • Code review checks for template fields that accept directives, filters, function calls, or executable expressions from untrusted users.
  • Policy enforcement requiring approved template syntax and rejecting dynamic evaluation outside designated sandboxed components.
  • Runtime monitoring for unusual process launches, shell commands, file access, or outbound connections by the web server process after template rendering.
  • Audit review of template creation, modification, and incident-rendering events.
  • Automated security review tools can help identify template injection and authorization-control patterns during development.

Sources

SourceLink
github.comgithub.com/cachethq/cachet/issues/4621
vulncheck.comvulncheck.com/advisories/cachet-authenticated-server-side-template-injection-rce

Frequently asked

questions

It may be exploitable through the application interface when an authenticated user has permission to create or modify incident templates and a vulnerable rendering path processes the content.

Authentication alone may not be sufficient. The account generally needs access to the relevant template-management function, and exploitation depends on the application's authorization configuration.

Do not evaluate user-controlled content as executable template logic. Use a restricted rendering model that supports only explicitly approved fields and filters, with contextual output escaping and sandboxing.

Enforce least-privilege authorization for template management, review dynamic template features during code review, monitor rendering behavior, and run the application with minimal operating-system privileges.

Find out what's already
exploitable in your codebase.