ghsa-58jc-rcg5-95f3
Vulnerability from github
Published
2025-12-26 17:30
Modified
2025-12-27 01:08
Severity ?
7.3 (High) - CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N
Summary
n8n's Possible Stored XSS in "Respond to Webhook" Node May Execute Outside iframe Sandbox
Details

Summary

A stored Cross-Site Scripting (XSS) vulnerability may occur in n8n when using the “Respond to Webhook” node. When this node responds with HTML content containing executable scripts, the payload may execute directly in the top-level window, rather than within the expected sandbox introduced in version 1.103.0.

This behavior can enable a malicious actor with workflow creation permissions to execute arbitrary JavaScript in the context of the n8n editor interface.

While session cookies (n8n-auth) are marked HttpOnly and cannot be directly exfiltrated, the vulnerability can facilitate Cross-Site Request Forgery (CSRF)-like actions from within the user’s authenticated session, potentially allowing:

  • Unauthorized reading of sensitive workflow data or execution history.
  • Unauthorized modification or deletion of workflows.
  • Insertion of malicious workflow logic or external data exfiltration steps.

n8n instances that allow untrusted users to create workflows are particularly impacted.

Patches

The vulnerability has been patched in v.1.114.0.

Workarounds

  • Restrict workflow creation and modification privileges to trusted users only.
  • Avoid using untrusted HTML responses in the “Respond to Webhook” node.
  • Use an external reverse proxy or HTML sanitizer to filter responses that include executable scripts.
Show details on source website

To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "npm",
        "name": "n8n"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.114.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2025-61914"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-79"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2025-12-26T17:30:19Z",
    "nvd_published_at": "2025-12-26T22:15:51Z",
    "severity": "HIGH"
  },
  "details": "### Summary\nA stored Cross-Site Scripting (XSS) vulnerability may occur in n8n when using the \u201cRespond to Webhook\u201d node.\nWhen this node responds with HTML content containing executable scripts, the payload may execute directly in the top-level window, rather than within the expected sandbox introduced in version 1.103.0.\n\nThis behavior can enable a malicious actor with workflow creation permissions to execute arbitrary JavaScript in the context of the n8n editor interface.\n\nWhile session cookies (`n8n-auth`) are marked `HttpOnly` and cannot be directly exfiltrated, the vulnerability can facilitate Cross-Site Request Forgery (CSRF)-like actions from within the user\u2019s authenticated session, potentially allowing:\n\n- Unauthorized reading of sensitive workflow data or execution history.\n- Unauthorized modification or deletion of workflows.\n- Insertion of malicious workflow logic or external data exfiltration steps.\n\nn8n instances that allow untrusted users to create workflows are particularly impacted.\n\n### Patches\nThe vulnerability has been patched in v.1.114.0.\n\n### Workarounds\n- Restrict workflow creation and modification privileges to trusted users only.\n- Avoid using untrusted HTML responses in the \u201cRespond to Webhook\u201d node.\n- Use an external reverse proxy or HTML sanitizer to filter responses that include executable scripts.",
  "id": "GHSA-58jc-rcg5-95f3",
  "modified": "2025-12-27T01:08:11Z",
  "published": "2025-12-26T17:30:19Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/n8n-io/n8n/security/advisories/GHSA-58jc-rcg5-95f3"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-61914"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/n8n-io/n8n"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "n8n\u0027s Possible Stored XSS in \"Respond to Webhook\" Node May Execute Outside iframe Sandbox"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.