Security readout for executives and security teams
Plain-English summary
Flowise 3.0.1 has a critical authentication bypass where a registration API endpoint is not protected. An outside attacker could create an account without credentials and then use the system’s API as an authenticated user. Treat internet-facing Flowise instances as high priority.
Executive priority
Prioritize this within emergency patch or containment workflows for exposed Flowise systems. The business risk is unauthorized administrative-style API access to automation workflows and connected data or services.
Technical view
CVE-2025-71327 is CWE-306 in Flowise 3.0.1. The unprotected /api/v1/account/register endpoint allows unauthenticated remote account creation, leading to authenticated access and full API access according to the provided advisory text. CVSS v4.0 is 9.3 critical.
Likely exposure
Highest risk is Flowise 3.0.1 reachable from untrusted networks or the internet. Internal-only deployments are still exposed to any actor with network reach to the application.
Exploitation context
No active exploitation is confirmed in the provided sources, and the CVE is not listed as KEV. Exploitation appears low-complexity because it is network-accessible, requires no privileges, and no user interaction per the CVSS vector.
Researcher notes
Evidence is limited to the CVE bundle, GitHub advisory reference, and VulnCheck advisory reference. The bundle names Flowise 3.0.1 as affected and default status as unaffected. Do not assume other versions are affected without vendor confirmation.
Mitigation direction
- Identify any Flowise 3.0.1 deployments immediately.
- Check the Flowise GitHub advisory for official remediation guidance.
- Restrict Flowise access to trusted networks until remediated.
- Block public access to the registration API endpoint where feasible.
- Review and remove unexpected accounts created on Flowise instances.
Validation and detection
- Confirm deployed Flowise version and exposure path.
- Check whether Flowise is reachable from the internet.
- Review logs for access to /api/v1/account/register.
- Audit recently created user accounts for unknown owners.
- Review API activity from newly created or suspicious accounts.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-306: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2025-71327 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.3 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N——VulnCheckCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N3.95.2VulnCheckVulnerability scoring details
Base CVSS 4.0 score
9.3CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
Base CVSS 3.1 score
9.1CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- GitHub Security Advisory (GHSA-v5w9-prxf-w882)CVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: Flowise - Authentication Bypass via Unprotected Registration EndpointCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Missing Authentication for Critical Function
Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.