CVE-2025-61913

[Flowise] WriteFileTool arbitrary file write vulnerability

Verified by Precogs Threat Research
Last Updated: Nov 7, 2025
Base Score
9.5CRITICAL

Executive Summary

CVE-2025-61913 is a critical severity vulnerability affecting appsec, ai-code, pii-secrets. It is classified as Path Traversal. Ensure your systems and dependencies are patched immediately to mitigate exposure risks.

Precogs AI Insight

"Precogs AI Analysis Engine identifies web application vulnerabilities through semantic code analysis, detecting injection flaws, broken authentication, and insecure data flows across your entire codebase."

Exploit Probability
High (84%)
Public POC
Available
Exploit Probability
High (84%)
Public POC
Available
Affected Assets
appsecai codepii secretsFlowiseCWE-22

What is this vulnerability?

CVE-2025-61913 is categorized as a critical Path Traversal flaw. Based on our vulnerability intelligence, this issue occurs when the application fails to securely handle untrusted data boundaries.

Summary

The WriteFileTool in Flowise does not restrict the file path for reading, allowing authenticated attackers to exploit this vulnerability to .

This architectural defect enables adversaries to bypass intended security controls, directly manipulating the application's execution state or data layer. Immediate strategic intervention is required.

Risk Assessment

MetricValue
CVSS Base Score9.5 (CRITICAL)
Vector StringN/A
PublishedOctober 8, 2025
Last ModifiedNovember 7, 2025
Related CWEsCWE-22

Impact on Systems

Sensitive File Disclosure: Unauthorized access to critical configuration files (/etc/passwd, .env files, private SSH keys).

Application Source Leak: Attackers can download proprietary source code and hardcoded credentials.

Remote Code Execution: By combining with log poisoning, attackers can write PHP/JSP shells into web-accessible directories.

How to fix this issue?

Implement the following strategic mitigations immediately to eliminate the attack surface.

1. Indirect References Avoid using direct file paths. Utilize indirect references (like database IDs) mapped to backend files.

2. Strict Path Resolution If direct paths are required, resolve the absolute path and rigorously verify the path starts with the expected base directory using native OS path resolving functions.

3. Chroot Jails Confine the application processes to highly restricted directory structures (chroot) with minimum readable boundaries.

Vulnerability Signature

// Vulnerable File Access
import os
def get_image(request):
    filename = request.GET.get('file')
    # VULNERABLE: No validation preventing moving upwards in the directory tree
    filepath = os.path.join('/var/www/images/', filename)
    return open(filepath, 'rb').read()

// EXPLOIT PAYLOAD: ?file=../../../../../../../../etc/passwd

References and Sources

Related Vulnerabilitiesvia CWE-22