CVE-2026-54303: n8n Reflected XSS in Meta & Teams Triggers (v2.24.0 Fix)
n8n, an open source workflow automation platform, contains a reflected cross-site scripting (XSS) vulnerability in its Meta and Microsoft Teams trigger node endpoints. When a logged-in n8n user clicks a specially crafted link, the endpoint reflects unsanitized query parameters directly into the HTTP response. Because the application lacks Content-Security-Policy headers, an attacker's malicious JavaScript executes in the context of the n8n application, potentially allowing session hijacking, credential theft, or unauthorized workflow modifications. The vulnerability affects all versions prior to 2.24.0.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 5.4 MEDIUM · CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
- Weaknesses (CWE)
- CWE-79
- Affected products
- 1 configuration(s)
- Published / Modified
- 2026-06-23 / 2026-06-25
NVD description (verbatim)
n8n is an open source workflow automation platform. Prior to 2.24.0, an endpoint in the Meta and Microsoft Teams trigger nodes reflects a query parameter into the HTTP response without sanitization or Content-Security-Policy headers, enabling reflected XSS in the n8n origin when a logged-in user visits a crafted URL. This vulnerability is fixed in 2.24.0.
1 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
The vulnerability exists in the Meta and Microsoft Teams trigger node endpoints, which fail to sanitize user-supplied query parameters before reflecting them in HTTP responses. An attacker crafts a URL containing malicious JavaScript within a query parameter, then tricks a logged-in n8n user into visiting it. Without input validation or output encoding, the JavaScript executes in the user's browser with the privileges of the n8n application. The absence of restrictive Content-Security-Policy headers further eliminates a secondary defense mechanism. This is a classic reflected XSS (CWE-79) scenario where the payload traverses the network on each request rather than being stored server-side.
Business impact
Successful exploitation allows attackers to impersonate authenticated users, steal session tokens or API credentials, modify or delete workflows without audit trails, access sensitive data flowing through automation processes, or redirect users to phishing pages. For organizations using n8n to orchestrate critical business processes—such as financial data integration, customer onboarding, or internal system synchronization—compromise of user sessions could disrupt operational continuity or expose regulated data. The attack requires user interaction (clicking a link), which may limit mass-scale exploitation but increases risk in targeted spear-phishing campaigns.
Affected systems
n8n versions prior to 2.24.0 are vulnerable. The issue is specific to the Meta and Microsoft Teams trigger nodes, meaning deployments using only other trigger types are not affected by this particular endpoint flaw. Both self-hosted and cloud-deployed instances of n8n are vulnerable if running unpatched versions. Open source users, commercial license holders, and free tier users on n8n Cloud are all in scope.
Exploitability
Exploitability is straightforward: an attacker constructs a phishing URL and sends it to a known n8n user. If that user is logged into n8n and clicks the link, malicious JavaScript runs immediately in their session context. No authentication bypass, no complex tricks, and no need for special network position. However, the attack does require user interaction and prior knowledge that the target uses n8n, which moderates the overall risk. The CVSS score of 5.4 (MEDIUM) reflects this balance: network-accessible, low complexity, but dependent on user action and limited to information disclosure and integrity impacts without availability or confidentiality at system level.
Remediation
Upgrade n8n to version 2.24.0 or later immediately. This release patches the endpoint to sanitize query parameters and implements Content-Security-Policy headers to prevent inline script execution. After patching, verify that the Meta and Microsoft Teams trigger nodes function correctly in your workflows. No configuration changes are required; the fix is applied automatically upon upgrade. Organizations should prioritize patching in environments where external users might be socially engineered into clicking untrusted links.
Patch guidance
For self-hosted deployments: update your n8n installation to version 2.24.0 using your standard deployment mechanism (Docker, npm, package manager, or source build). Test the upgrade in a non-production environment first to ensure compatibility with any custom nodes or integrations. For n8n Cloud users: updates are deployed automatically by n8n; verify that your account is running 2.24.0 or later via the application settings or admin panel. After upgrade, confirm that workflows using Meta and Microsoft Teams triggers continue to function and that no manual workflow adjustments are needed.
Detection guidance
Monitor HTTP access logs for suspicious query parameters in requests to Meta and Microsoft Teams trigger node endpoints (typically paths containing 'meta' or 'teams' in the URI). Look for encoded or obfuscated JavaScript payloads, script tags, or event handlers in query strings. Check browser console logs and developer tools on user machines for XSS attempts. Web Application Firewalls (WAF) can be configured to block requests containing common XSS patterns in query parameters. Implement Content-Security-Policy headers across your n8n deployment to log and prevent inline script execution even if input validation is bypassed. Audit user account activity logs for unusual session tokens, workflow changes, or API access patterns that may indicate compromised sessions.
Why prioritize this
Although the CVSS score is MEDIUM (5.4) and the vulnerability is not listed on CISA's Known Exploited Vulnerabilities catalog, this should be prioritized for prompt patching because XSS vulnerabilities targeting authenticated users are reliable attack vectors in spear-phishing campaigns. The fix is simple and non-disruptive (upgrade to 2.24.0), and the vulnerability directly impacts session security for users of a workflow automation platform that may handle sensitive integrations. The confluence of straightforward exploitability, social engineering potential, and the business-critical nature of workflow automation warrants prioritization in patch management schedules even at MEDIUM severity.
Risk score, explained
The CVSS 3.1 score of 5.4 reflects a network-accessible vulnerability requiring low attack complexity and user interaction (PR=L, UI=R). Impacts are limited to confidentiality and integrity of the user's session and data visible to that session (C:L, I:L), with no system-wide availability impact (A:N). The scope is changed (S:C) because the vulnerability affects resources outside the vulnerable component itself—the attacker can influence the n8n application's behavior from the user's perspective. This MEDIUM rating does not capture the reputational and operational risk of a workflow automation platform being compromised; it reflects only the technical bounds of XSS impact per the CVSS methodology. Organizations should evaluate their own risk tolerance based on the criticality of n8n to their operations.
Frequently asked questions
Can this vulnerability be exploited if a user is not logged into n8n?
No. The vulnerability requires the user to have an active authenticated session. If a user visits the malicious link while logged out, the payload may still reflect in the response, but it executes in an unauthenticated context with no access to user data or workflows. An attacker would need to target logged-in users specifically.
Does this affect n8n Cloud, self-hosted, or both?
Both. The vulnerability exists in the underlying n8n codebase regardless of deployment model. Self-hosted users must manually upgrade to 2.24.0. n8n Cloud users receive the patch automatically, but should verify their instance is running the patched version.
Are only Meta and Microsoft Teams triggers affected, or are other trigger types vulnerable too?
Only the Meta and Microsoft Teams trigger node endpoints are vulnerable due to the specific code path that reflects unsanitized query parameters. Other trigger types do not share this vulnerability, though it is good practice to patch all n8n instances to benefit from any other security improvements in 2.24.0.
What should we do if we suspect our n8n instance was exploited via this vulnerability?
Immediately rotate API keys, session tokens, and credentials for any external systems connected to n8n workflows. Review audit logs for unauthorized workflow modifications or data access. Check for any new user accounts or permission changes. If you manage n8n Cloud, contact n8n support. For self-hosted instances, upgrade to 2.24.0, restart the service, and monitor for further suspicious activity.
This analysis is based on the official CVE-2026-54303 disclosure and n8n vendor advisories. Verify all patch versions, affected products, and remediation steps against the authoritative n8n security documentation and release notes before deploying patches. SEC.co does not provide exploit code or detailed proof-of-concept instructions. Organizations should conduct their own risk assessment and testing in accordance with their security policies and business requirements. This information is provided for educational and defensive purposes only. Source: NVD (public-domain), retrieved 2026-07-28. Analysis generated by SEC.co (claude-haiku-4-5).
Related vulnerabilities
- CVE-2026-54301MEDIUMn8n Webhook XSS Vulnerability Bypasses CSP (CVSS 5.4)
- CVE-2026-54302MEDIUMn8n Chat Trigger Stored XSS Vulnerability
- CVE-2016-20070MEDIUMPrivilege Escalation & Stored XSS in WordPress Booking Calendar Contact Form 1.0.23
- CVE-2018-25384MEDIUMStored XSS in Wikidforum 2.20 Allows Authenticated Attackers to Inject Malicious Scripts
- CVE-2019-25731MEDIUMStored XSS in Zuz Music 2.1 Contact Form
- CVE-2019-25737MEDIUMStored XSS in Live Chat Unlimited 2.8.3 – Admin Session Compromise
- CVE-2019-25739MEDIUMGigToDo 1.3 Stored XSS Vulnerability in Proposal Descriptions
- CVE-2019-25742MEDIUMStored XSS in Zoner Real Estate WordPress Theme 4.1.1 – Admin Account Compromise Risk