Quick answers
- Is CVE-2026-113712 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-113712 being exploited in the wild.
- How severe is CVE-2026-113712?
- Medium severity, with a CVSS score of 4, published 20 October 2026.
- Which products and versions are affected?
- Cachethq Cachet 2.4.1 and earlier; v3; cachethq/cachet (Packagist) <= 2.4.1, ECOSYSTEM:introduced=0,last_affected=2.4.1.
- Is there a fix for CVE-2026-113712?
- Yes: fixed in Commits 23adbb88ffa819f92be4a905ff1d812670d980a2 and 57b44a8bac0b250b0d5751e93e0349070d14606e in cachethq/core. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-113712 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-113712?
- Check whether you run Cachethq Cachet or cachethq/cachet (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Commits 23adbb88ffa819f92be4a905ff1d812670d980a2 and 57b44a8bac0b250b0d5751e93e0349070d14606e in cachethq/core
Technical details
A stored XSS vulnerability exists in the incident creation form's Name and Message fields, which do not properly sanitize HTML event handler attributes. Although <script> tags are filtered, event-based payloads such as <img src=x onerror="..."> bypass the protection. The vulnerability affects the /dashboard/incidents/ endpoint and requires authentication to inject; payloads execute when any user views the public status page. Commits 23adbb8 and 57b44a8 in cachethq/core patch the issue by sanitizing user-authored Markdown and stripping raw HTML.
Affected products
- cachethq Cachet 2.4.1 and earlier; v3
Identifiers
- CVE-2026-113712
- GHSA-x397-5hrv-j9m9
Timeline
- 2026-08-27: disclosed
- 2026-10-20: advisory