GHSA-m837-xvxr-vqwg
Suggest an improvement- Source
- https://github.com/advisories/GHSA-m837-xvxr-vqwg
- Import Source
- https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/05/GHSA-m837-xvxr-vqwg/GHSA-m837-xvxr-vqwg.json
- JSON Data
- https://api.osv.dev/v1/vulns/GHSA-m837-xvxr-vqwg
- Aliases
- Published
- 2026-05-20T15:38:02Z
- Modified
- 2026-07-08T08:27:17.428824259Z
- Severity
-
- 6.9 (Medium) CVSS_V4 - CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N CVSS Calculator
- Summary
- Flowise: Hardcoded CORS wildcard on TTS endpoint enables cross-origin credential abuse from any webpage
- Details
-
Summary
The TTS generation endpoint sets
Access-Control-Allow-Origin: *as a hardcoded response header, independent of the server's CORS configuration. This enables any webpage to make cross-origin requests to generate speech using stored credentials.Root Cause
// packages/server/src/controllers/text-to-speech/index.ts:83 res.setHeader('Access-Control-Allow-Origin', '*') res.setHeader('Access-Control-Allow-Headers', 'Cache-Control')Impact
- 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
Suggested Fix
Remove the hardcoded CORS wildcard and let the server's CORS middleware handle the headers:
// Remove these lines: // res.setHeader('Access-Control-Allow-Origin', '*') // res.setHeader('Access-Control-Allow-Headers', 'Cache-Control')
References
packages/server/src/controllers/text-to-speech/index.tsline 83
- Database specific
{ "github_reviewed": true, "severity": "MODERATE", "cwe_ids": [ "CWE-942" ], "nvd_published_at": null, "github_reviewed_at": "2026-05-20T15:38:02Z" }- References
Affected packages
npm / flowise
Package
- Name
- flowise
- View open source insights on deps.dev
- Purl
- pkg:npm/flowise