n8n: Reflected XSS via Facebook, WhatsApp, and Microsoft Teams Trigger Webhook Verification Endpoints
CVE-2026-54303 · GHSA-h86q-fx34-gfjr · published 2026-06-16 · updated 2026-07-20
- Severity
- Medium
- CVSS score
- 7.6
- Chance of exploitation (EPSS)
- 0.23%
- Fixed in
- 2.24.0
- Exploitation No known exploitation
- Automatable No
- Technical impact Partial
- CISA SSVC
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.
Upgrade n8n to 2.24.0 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
The issue has been fixed in n8n version 2.24.0. Users should upgrade to this version or later to remediate the vulnerability.
If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Limit workflow creation and activation permissions to fully trusted users only. Disable the affected nodes by adding n8n-nodes-base.facebookTrigger, n8n-nodes-base.whatsAppTrigger, n8n-nodes-base.facebookLeadAdsTrigger, and n8n-nodes-base.microsoftTeamsTrigger to the NODES_EXCLUDE environment variable. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| n8n | npm | < 2.24.0 | 2.24.0 |
- CriticalJupyter Server: Stored XSS in `NbconvertFileHandler` / `NbconvertPostHandler` via missing `sandbox` CSPjupyter-server
- CriticalMalicious website can execute commands on the local system through XSS in the OpenCode web UIopencode-ai
- CriticalFlowise is vulnerable to stored XSS via "View Messages" allows credential theft in FlowiseAI admin panelflowise
- CriticalMLFlow Cross-site Scripting vulnerability leads to client-side Remote Code Executionmlflow
- CriticalCross-site Scripting in MLFlowmlflow
- HighPraisonAI: Prompt Injection Defense Bypassed for HIGH-Level Threatspraisonai
- Criticaln8n Vulnerable to Remote Code Execution via Expression Injectionn8n, n8nExploited
- Criticaln8n Has an Arbitrary File Read via Git Noden8n, n8n, n8n
- Criticaln8n: HTTP Request Node Pagination Prototype Pollution to RCEn8n, n8n, n8n
- Criticaln8n Has an XML Node Prototype Pollution Patch Bypassn8n, n8n, n8n
- Criticaln8n has XML Node Prototype Pollution that to RCEn8n, n8n, n8n
- Criticaln8n has Prototype Pollution in XML Webhook Body Parser that Leads to RCEn8n, n8n, n8n
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.