CVE-2025-61913
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedFlowise is a drag & drop user interface to build a customized large language model flow. In versions prior to 3.0.8, WriteFileTool and ReadFileTool in Flowise do not restrict file path access, allowing authenticated attackers to exploit this vulnerability to read and write arbitrary files to any path in the file system, potentially leading to remote command execution. Flowise 3.0.8 fixes this vulnerability.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceFlowise versions before 3.0.8 contain path traversal vulnerabilities in WriteFileTool and ReadFileTool that lack proper file path restrictions. Authenticated attackers can read and write files to arbitrary filesystem paths, enabling potential remote command execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 3.0.8CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Flowise installation and versionLocate the Flowise installation directory and check the version.json or package.json file, or run 'npm list flowise' or 'flowise --version' if CLI is availableAffected if The installed version is any version before 3.0.8
-
Determine if WriteFileTool is exposedReview the Flowise chatflows or API configurations for any deployed flows that include the WriteFileTool component. Check the components list in the Flowise UI or configuration files under the flows or storage directoriesAffected if WriteFileTool is enabled and accessible to authenticated users in any deployed flow
-
Determine if ReadFileTool is exposedReview the Flowise chatflows or API configurations for any deployed flows that include the ReadFileTool component. Check the components list in the Flowise UI or configuration files under the flows or storage directoriesAffected if ReadFileTool is enabled and accessible to authenticated users in any deployed flow
-
Check for file path restriction configurationInspect the Flowise configuration file (typically flowise.json or .env) for any settings related to file access restrictions, allowed paths, or sandboxing for the file toolsAffected if No file path allowlist or restriction is configured for WriteFileTool and ReadFileTool
You are affected if Flowise version is below 3.0.8 AND either WriteFileTool or ReadFileTool is deployed in an accessible flow without file path restrictions configured.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped3.0.8
Upgrade Flowise to version 3.0.8 or later. Additionally, audit logs for signs of exploitation, reset credentials for compromised accounts, and review file system permissions to limit the impact of any future path traversal attempts.
Flowise 3.0.8
- Backup your Flowise data and configuration files before upgrading
- Stop the Flowise service to prevent data corruption during upgrade
- Upgrade Flowise to version 3.0.8 by pulling the latest Docker image or using your installation method (e.g., `docker pull flowiseai/flowise:latest` or package manager update)
- Verify the upgrade completed successfully by checking the version number in the Flowise UI or CLI
- Restart the Flowise service
- Confirm that WriteFileTool and ReadFileTool now properly restrict file path access
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-61913 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-61913 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data