n8n before 1.123.69 Stored XSS via Form Completion Page
n8n-io n8n
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| n8n-io n8n |
|
|
| n8n-io n8n |
|
|
| n8n-io n8n |
|
|
n8n-io n8n
| Product | Affected | Fixed in |
|---|---|---|
| n8n-io n8n |
|
|
| n8n-io n8n |
|
|
| n8n-io n8n |
|
|
n8n before 1.123.69, 2.33.4, and 2.34.1 contains a stored cross-site scripting vulnerability in the Form node's completion page. The completion page applied its sandboxing Content-Security-Policy only when respondWith was not set to 'redirect', but responseText was always rendered as raw HTML. An authenticated member could set respondWith to 'redirect' via an expression while keeping responseText populated, causing the completion page to serve unsanitized HTML and script from the n8n origin. Any visitor who submitted the resulting public form would have that script execute same-origin with their session.
From the CVE record · VulnCheck
The Form node completion page can render unsanitized HTML and script from the n8n origin when an authenticated member sets respondWith to 'redirect' through an expression while leaving responseText populated. A visitor who submits the resulting public form can have that script execute with their session.
Teams running n8n versions before the fixed releases 1.123.69, 2.33.4, or 2.34.1 should check their installations.