Cachet has Stored XSS in Incident Component

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

4.8 · CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N · score source

EPSS

• CVE-2026-113712: 0.46% estimated exploitation activity in the next 30 days; percentile 39.87 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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: Step 2 — Cookie/token exfiltration: Step 3 — Forced redirect to sensitive page: 5. Save the incident 6. Navigate to the public status page 7. Payload executes in the victim's browser Payload 1 <img…

Published by the source

20 Oct 2026, 21:09 UTC

Last modified by the source

20 Oct 2026, 21:15 UTC

Source last checked

26 Oct 2026, 14:53 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-x397-5hrv-j9m9

2. Revision 2 · amended · 25 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-x397-5hrv-j9m9

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-113712

Advisory: Cachet has Stored XSS in Incident Component
IDs: CVE-2026-113712, GHSA-x397-5hrv-j9m9
Record: https://patchnext.com/advisories/cve-2026-113712 (revision 3, source checked 26 Oct 2026, 14:53 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist cachethq/cachet: affected <= 2.4.1

## Suggested inspection (read-only)
- Packagist cachethq/cachet: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on cachethq/cachet.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-x397-5hrv-j9m9 (OSV record GHSA-x397-5hrv-j9m9 lists affected ranges: Packagist cachethq/cachet >=0 <=2.4.1)
- Verified: https://github.com/advisories/GHSA-x397-5hrv-j9m9 (GitHub-reviewed advisory GHSA-x397-5hrv-j9m9 lists affected ranges: Packagist cachethq/cachet >=0 <=2.4.1)

Commands are suggestions: review each one before running it.