Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-61914: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in n8n-io n8n

0
High
VulnerabilityCVE-2025-61914cvecve-2025-61914cwe-79
Published: Fri Dec 26 2025 (12/26/2025, 21:48:59 UTC)
Source: CVE Database V5
Vendor/Project: n8n-io
Product: n8n

Description

CVE-2025-61914 is a stored Cross-Site Scripting (XSS) vulnerability in the n8n workflow automation platform versions prior to 1. 114. 0. It arises when the “Respond to Webhook” node returns HTML content containing executable scripts, which execute in the top-level window instead of a sandboxed environment. This allows an attacker with workflow creation privileges to run arbitrary JavaScript within the n8n editor interface. The vulnerability has a CVSS score of 7. 3 (high severity) and requires user interaction and privileges to exploit. Mitigations include upgrading to version 1. 114. 0 or later, restricting workflow creation rights to trusted users, avoiding untrusted HTML responses, and using external sanitization or reverse proxies.

AI-Powered Analysis

AILast updated: 12/26/2025, 22:09:47 UTC

Technical Analysis

CVE-2025-61914 is a high-severity stored Cross-Site Scripting (XSS) vulnerability affecting n8n, an open-source workflow automation platform, in versions prior to 1.114.0. The issue specifically involves the “Respond to Webhook” node, which when configured to respond with HTML content containing executable scripts, fails to properly sandbox this content. Instead of executing scripts within a secure iframe or sandboxed environment (introduced in version 1.103.0), the scripts execute directly in the top-level window context of the n8n editor interface. This improper neutralization of input (CWE-79) allows a malicious actor who has permissions to create or modify workflows to inject and execute arbitrary JavaScript code. Such code execution can lead to theft of session tokens, manipulation of workflows, or further pivoting within the n8n environment. The vulnerability requires the attacker to have workflow creation privileges and some user interaction (triggering the webhook response). Although no known exploits are reported in the wild yet, the vulnerability is significant due to the potential for privilege escalation and persistent code execution within the automation platform. The issue was addressed in n8n version 1.114.0 by enforcing proper sandboxing of webhook responses. Workarounds include restricting workflow creation/modification to trusted users, avoiding untrusted HTML in webhook responses, and deploying external reverse proxies or HTML sanitizers to filter malicious scripts.

Potential Impact

For European organizations, this vulnerability poses a risk to the integrity and confidentiality of automation workflows managed via n8n. Successful exploitation could allow attackers to execute arbitrary JavaScript within the n8n editor, potentially leading to unauthorized access to sensitive workflow data, manipulation of automation processes, and disruption of business-critical operations. Since n8n is used for integrating various services and automating tasks, compromise could cascade into other connected systems, amplifying the impact. Organizations relying on n8n for internal or customer-facing automation workflows may face data leakage, workflow sabotage, or unauthorized privilege escalation. The vulnerability does not directly affect availability but can undermine trust in automation integrity. Given the increasing adoption of workflow automation in Europe, especially in sectors like finance, manufacturing, and public services, the impact could be significant if left unmitigated.

Mitigation Recommendations

1. Upgrade all n8n instances to version 1.114.0 or later, where the vulnerability is patched with proper sandboxing of webhook responses. 2. Restrict workflow creation and modification privileges strictly to trusted and vetted users to reduce the attack surface. 3. Avoid using untrusted or user-supplied HTML content in the “Respond to Webhook” node to prevent injection of executable scripts. 4. Deploy an external reverse proxy or web application firewall (WAF) configured to sanitize or block HTML responses containing executable scripts from n8n webhook endpoints. 5. Implement monitoring and alerting on workflow changes and webhook responses to detect anomalous activity. 6. Educate administrators and developers on secure workflow design and the risks of injecting untrusted content. 7. Regularly audit user permissions and workflow configurations to ensure compliance with least privilege principles.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2025-10-03T22:21:59.614Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 694f040e33784cecd498bd15

Added to database: 12/26/2025, 9:54:22 PM

Last enriched: 12/26/2025, 10:09:47 PM

Last updated: 12/27/2025, 1:09:22 AM

Views: 5

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats