---
id: CVE-2026-54303
title: >-
  n8n: Reflected XSS via Facebook, WhatsApp, and Microsoft Teams Trigger Webhook
  Verification Endpoints
summary: >-
  n8n: Reflected XSS via Facebook, WhatsApp, and Microsoft Teams Trigger Webhook
  Verification Endpoints
severity: medium
cvss: 7.6
cwe:
  - CWE-79
vendor: n8n
product: n8n
ecosystem: npm
affected:
  - n8n < 2.24.0
patched:
  - n8n 2.24.0
published: '2026-06-16'
updated: '2026-06-16'
source: GHSA
sourceUrl: 'https://github.com/advisories/GHSA-h86q-fx34-gfjr'
references:
  - url: 'https://github.com/n8n-io/n8n/security/advisories/GHSA-h86q-fx34-gfjr'
  - url: 'https://github.com/advisories/GHSA-h86q-fx34-gfjr'
tags:
  - ghsa
  - npm
epss: 0.00231
epssPercentile: 0.12547
ingestedAt: '2026-06-29T14:31:47.476Z'
---

## Overview

## Impact
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.

## Patches
The issue has been fixed in n8n version 2.24.0. Users should upgrade to this version or later to remediate the vulnerability.

## Workarounds
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.

## Affected packages

- `n8n < 2.24.0`

## Remediation

Upgrade to a patched release:

- `n8n 2.24.0`