Summary
Detection Method: Kolega.dev Deep Code Scan
| Attribute | Value |
|---|---|
| Location | packages/server/src/enterprise/middleware/passport/index.ts:55 |
| Practical Exploitability | High |
| Developer Approver | [email protected] |
Description
Express session secret has a weak default value 'flowise' when EXPRESS_SESSION_SECRET is not set.
Affected Code
secret: process.env.EXPRESS_SESSION_SECRET || 'flowise'
Evidence
The default session secret 'flowise' is publicly visible and weak. Session cookies signed with this secret can be forged by attackers.
Notes
The Express session secret defaults to the string 'flowise' when EXPRESS_SESSION_SECRET is not set (line 55). This secret is used to sign session cookies via express-session middleware. Since 'flowise' is publicly visible in the source code, an attacker can forge valid session cookies to impersonate any user without authentication. The .env.example file has this commented out (# EXPRESS_SESSION_SECRET=flowise), implying it's optional, which compounds the risk. Unlike development-only defaults, this code path is active in production if the environment variable is not set. The application should require EXPRESS_SESSION_SECRET to be explicitly configured with a cryptographically strong random value and fail to start otherwise.
Impact
Session hijacking and forgery - attackers can create arbitrary session cookies to impersonate any user, bypassing all authentication mechanisms.
Credentials are embedded in source code or a binary, making them accessible to anyone who can read the artifact. Typical impact: unauthorized access using the static credential.
GHSA-2QQC-P94C-HXWH has a CVSS score of 5.6 (Medium). The vector is requires local access, high privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.1.0); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Require EXPRESS_SESSION_SECRET to be set with a strong random value. Throw an error on startup if not configured. Use cryptographically strong random strings (minimum 256 bits).
Frequently Asked Questions
- What is GHSA-2QQC-P94C-HXWH? GHSA-2QQC-P94C-HXWH is a medium-severity use of hard-coded credentials vulnerability in flowise (npm), affecting versions <= 3.0.13. It is fixed in 3.1.0. Credentials are embedded in source code or a binary, making them accessible to anyone who can read the artifact.
- How severe is GHSA-2QQC-P94C-HXWH? GHSA-2QQC-P94C-HXWH has a CVSS score of 5.6 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of flowise are affected by GHSA-2QQC-P94C-HXWH? flowise (npm) versions <= 3.0.13 is affected.
- Is there a fix for GHSA-2QQC-P94C-HXWH? Yes. GHSA-2QQC-P94C-HXWH is fixed in 3.1.0. Upgrade to this version or later.
- Is GHSA-2QQC-P94C-HXWH exploitable, and should I be worried? Whether GHSA-2QQC-P94C-HXWH is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-2QQC-P94C-HXWH is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-2QQC-P94C-HXWH? Upgrade
flowiseto 3.1.0 or later.