Arbitrary file writes via unvalidated upload filenames
Published Nov 19, 2025 · Updated Nov 20, 2025
Path traversal in FileCodeBox 2.2 and earlier allows remote attackers to write arbitrary files through unauthenticated uploads. SystemFileStorage.save_file in core/storage.py joins an attacker-controlled multipart filename to its storage root without validating traversal sequences before creating directories and writing the file. The /share/file/ endpoint needs no authorization, but exploitation requires local filesystem storage and writes with the service process's filesystem permissions.
Summary
What happened
Path traversal in FileCodeBox 2.2 and earlier allows remote attackers to write arbitrary files through unauthenticated uploads. SystemFileStorage.save_file in core/storage.py joins an attacker-controlled multipart filename to its storage root without validating traversal sequences before creating directories and writing the file. The /share/file/ endpoint needs no authorization, but exploitation requires local filesystem storage and writes with the service process's filesystem permissions.
The record
- CVE
- CVE-2025-51661
- Published
- Nov 19, 2025
- Updated
- Nov 20, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-24, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 19, 2025CVE publishedPublication date reported by the CVE source.
- Nov 20, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Multipart filename traversal proof of conceptproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo