Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2026-54303: n8n: Reflected XSS via Facebook, WhatsApp, and Microsoft Teams Trigger Webhook Verification Endpoints

MediumCVSS 6.8 · v4.0—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 27/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No special conditions are required; it is repeatable.
  • Fixed version: n8n-io n8n 2.24.0.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to n8n-io n8n 2.24.0 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Jun 23, 2026
Updated
Oct 26, 2026
EPSS
0.2% · 14th percentile

Report tools

JSON

Action score

27

Monitor

Low priority for now.

CVSS
27 / 40 · 6.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_M
6.8
NVD has not scored this yet; the score shown is the CNA’s.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-54303

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Limit the impact of XSSCheck security headers

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Limit the impact of XSSCheck security headers

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
n8nn8n

Limit the impact of XSS

This is a cross-site scripting (XSS) vulnerability. A well-configured Content-Security-Policy doesn't fix it, but greatly reduces its impact. Check your site's CSP and other security headers for free.

Check security headers

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • n8n-io n8n

    • < 2.24.0affected

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • n8n n8nbefore 2.24.0

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
npmn8nbefore 2.24.02.24.0

Same product

n8n: all records

Other highest-scoring records for the same primary product.

  • CVE-2025-68613n8n Vulnerable to Remote Code Execution via Expression InjectionKEV
    95Now
  • CVE-2026-21858n8n Vulnerable to Unauthenticated File Access via Improper Webhook Request Handling
    63This week
  • CVE-2026-1470Authenticated users can bypass the Expression sandbox mechanism to achieve full remote code execution on n8n’s main node.
    45Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-56348Jun 22, 2026 · n8n - Credential Exfiltration via Allowed HTTP Request Domains Bypass in Dynamic Node Parameters Endpoint
    21Monitor
  • ← EarlierCVE-2026-56357Jun 22, 2026 · n8n - Webhook Forgery via Missing HMAC-SHA256 Signature Verification in GitHub Webhook Trigger
    25Monitor
  • Later →CVE-2026-54309Jun 23, 2026 · n8n: n8n MCP Browser HTTP Transport Exposes Unauthenticated Browser-Control Sessions
    35Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
n8n-io n8n2.24.0 · descriptionVendor (CNA)
npm:n8n2.24.0Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-4223550 days apartn8n: XSS via MCP OAuth client
    35Monitor
  • CVE-2026-27578118 days apartn8n Vulnerable to Stored XSS via Various Nodes
    34Monitor
  • CVE-2026-25051139 days apartn8n Improper CSP Enforcement in Webhook Responses May Allow Stored XSS
    34Monitor
  • CVE-2026-25054139 days apartn8n is Vulnerable to Stored Cross-Site Scripting via Markdown Rendering in Workflow UI
    34Monitor
  • CVE-2026-6559229 days apartn8n before 1.123.64 Stored DOM XSS via cachedResultUrl
    33Monitor
  • CVE-2026-7707258 days apartn8n before 1.123.69 Stored XSS via Form Completion Page
    33Monitor

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
A
Scope
X

CVSS vector

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Root cause

User content is inserted into the page as HTML. The browser interprets the content as code rather than data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
commentEl.innerHTML = comment.body;

Fixed

ts
commentEl.textContent = comment.body;

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records