GHSA-m5p9-xvxj-64c8
CRITICALGHSA-m5p9-xvxj-64c8 is a critical-severity (CVSS 9.6) Cross-site Scripting (XSS) vulnerability in flowise-embed. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-m5p9-xvxj-64c8 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Flowise and Flowise Chat Embed vulnerable to Stored Cross-site Scripting
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
flowisenpmDescription
Flowise < 2.1.1 suffers from a Stored Cross-Site vulnerability due to a lack of input sanitization in Flowise Chat Embed < 2.0.0.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | flowise-embed | all versions | 2.0.0 |
| 📦npm | flowise | all versions | 2.1.1 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for flowise-embed. 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-embed to 2.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m5p9-xvxj-64c8 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-m5p9-xvxj-64c8 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-m5p9-xvxj-64c8. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-m5p9-xvxj-64c8 in your dependencies?
O3 detects GHSA-m5p9-xvxj-64c8 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.