UTC
Medium

Flowise: Hardcoded CORS wildcard on TTS endpoint enables cross-origin credential abuse from any webpage

GHSA-m837-xvxr-vqwg · published 2026-05-20

Severity
Medium
CVSS score
6.9
Chance of exploitation (EPSS)
No CVE
Fixed in
3.1.2
What it is

Cross-origin credential abuse — any webpage can trigger TTS using stored credentials Bypasses the server's CORS policy (getCorsOptions()) which is otherwise restrictive by default Combined with Finding 3 (TTS credential abuse), enables drive-by credential abuse via malicious webpages

What to do

Upgrade flowise to 3.1.2 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.

Remove the hardcoded CORS wildcard and let the server's CORS middleware handle the headers: ---

Affected
PackageRegistryAffectedFixed in
flowisenpm<= 3.1.13.1.2

The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].