Headline

GHSA-hfmv-hhh3-43f2: Stored XSS in n8n Form Trigger allows Account Takeover via injected iframe and video/source

Impact

A stored Cross-Site Scripting (XSS) vulnerability was identified in n8n, specifically in the Form Trigger node’s HTML form element. An authenticated attacker can inject malicious HTML via an <iframe> with a srcdoc payload that includes arbitrary JavaScript execution. The attacker can also inject malicious Javascript by using <video> coupled <source> using an onerror event.

While using iframe or a combination of video and source tag, this vulnerability allows for Account Takeover (ATO) by exfiltrating n8n-browserId and session cookies from authenticated users who visit a maliciously crafted form. Using these tokens and cookies, an attacker can impersonate the victim and change account details such as email addresses, enabling full control over the account—especially if 2FA is not enabled.

Patches

The issue was addressed in PR #16329. Users should upgrade to version >=1.98.2.

Workarounds

Apart from updating to the fixed version, n8n instance administrators can:

Configure a reverse proxy to serve webhook requests from a different domain [docs].
Disable or restrict use of the Form Trigger node, particularly the HTML element type.
Use a Content Security Policy (CSP) to block execution of inline scripts and disallow use of srcdoc.

References

2 hours ago

ghsa

Open in Source

#xss #vulnerability #web #git #java #auth

Impact

A stored Cross-Site Scripting (XSS) vulnerability was identified in n8n, specifically in the Form Trigger node’s HTML form element. An authenticated attacker can inject malicious HTML via an <iframe> with a srcdoc payload that includes arbitrary JavaScript execution. The attacker can also inject malicious Javascript by using <video> coupled <source> using an onerror event.

While using iframe or a combination of video and source tag, this vulnerability allows for Account Takeover (ATO) by exfiltrating n8n-browserId and session cookies from authenticated users who visit a maliciously crafted form. Using these tokens and cookies, an attacker can impersonate the victim and change account details such as email addresses, enabling full control over the account—especially if 2FA is not enabled.

Patches

The issue was addressed in PR #16329. Users should upgrade to version >=1.98.2.

Workarounds

Apart from updating to the fixed version, n8n instance administrators can:

Configure a reverse proxy to serve webhook requests from a different domain [docs].
Disable or restrict use of the Form Trigger node, particularly the HTML element type.
Use a Content Security Policy (CSP) to block execution of inline scripts and disallow use of srcdoc.

References