High · published December 27, 2025
⚡ A sneaky XSS flaw lurks in n8n, letting workflow creators unleash JavaScript like confetti at a parade! 🎉 Think of n8n’s workflow like a restaurant kitchen, where only trusted chefs should be allowed to cook. If a rogue chef slips in a dangerous recipe, it could lead to a chaotic dining experience for everyone! This stored XSS vulnerability allows an attacker with workflow creation privileges to execute arbitrary JavaScript in the n8n editor interface. The consequences could be catastrophic: data theft, manipulation, or even taking over sessions — a recipe for disaster!
Think of n8n’s workflow like a restaurant kitchen, where only trusted chefs should be allowed to cook. If a rogue chef slips in a dangerous recipe, it could lead to a chaotic dining experience for everyone! In n8n versions prior to 1.114.0, the 'Respond to Webhook' node can process HTML content that executes scripts outside the intended sandbox, making it vulnerable to XSS attacks if untrusted content is delivered.
This stored XSS vulnerability allows an attacker with workflow creation privileges to execute arbitrary JavaScript in the n8n editor interface. The consequences could be catastrophic: data theft, manipulation, or even taking over sessions — a recipe for disaster! Upgrade to n8n version 1.114.0 immediately to close this vulnerability. Additionally, restrict workflow creation to trusted users and consider using an external reverse proxy or HTML sanitizer to filter out untrusted responses. Vigilance is key! You've got this! By following these steps, you'll have your n8n workflows fortified in no time! 🛡️
| Product | Versions | Fixed in |
|---|---|---|
| n8n/n8n | < 1.114.0 | 1.114.0 |