Security readout for executives and security teams
Plain-English summary
CVE-2025-71333 is a critical Flowise vulnerability that may let an unauthenticated attacker upload files outside intended directories. If a vulnerable Flowise instance uses local storage and is reachable, compromise could extend to remote code execution and server takeover. No active exploitation is stated in the provided sources.
Executive priority
Treat as urgent for any exposed Flowise deployment using local storage. The combination of unauthenticated access, critical severity, and possible server compromise creates material business risk. Prioritize inventory, exposure reduction, and vendor-guided remediation.
Technical view
Flowise through 2.2.4 has an arbitrary file upload issue in /api/v1/attachments when storageType is local. Path traversal in chatId and chatflowId can place files in arbitrary directories. The CVE maps to CWE-73 and carries CVSS 4.0 score 9.3. Provided affected metadata is inconsistent, so confirm against vendor advisory.
Likely exposure
Highest risk applies to internet-accessible Flowise deployments through 2.2.4 using local storage. Internal instances are still exposed if untrusted users or compromised systems can reach the attachments endpoint. Environments not using local storage appear less directly exposed based on the description.
Exploitation context
The issue requires no authentication, no user interaction, and low attack complexity according to the CVSS vector. Sources describe potential remote code execution and server compromise, but do not state known exploitation in the wild. It is not listed as KEV in the provided bundle.
Researcher notes
The provided data identifies Flowise through 2.2.4 and local storage as the key condition. However, affected-version metadata in the bundle is contradictory, listing defaultStatus unaffected and version 0. Validate against the GitHub advisory before making final scope decisions.
Mitigation direction
- Check the Flowise GitHub advisory for fixed versions or official remediation guidance.
- Prioritize updating Flowise deployments through 2.2.4 when vendor guidance confirms a fix.
- Limit access to Flowise and /api/v1/attachments to trusted networks where possible.
- Review whether storageType is set to local and reduce exposure if feasible.
- Monitor Flowise upload directories and application logs for suspicious file activity.
Validation and detection
- Inventory all Flowise deployments and record their versions.
- Confirm whether each deployment uses local storageType.
- Determine whether /api/v1/attachments is reachable from untrusted networks.
- Review logs for abnormal attachment uploads or traversal-like parameter values.
- Compare findings with the vendor advisory and CVE record.
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-73: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. 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 lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell 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-71333 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:H/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
1 official scoreWe 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:H/SC:N/SI:N/SA:N——VulnCheckVulnerability 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:H/SC:N/SI:N/SA: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-h42x-xx2q-6v6g)CVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: Flowise - Arbitrary File Upload via Unauthenticated /api/v1/attachments 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.
External Control of File Name or Path
External Control of File Name or Path represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.