CVE-2025-62510
📋 TL;DR
A regression in FileRise version 1.4.0 allows low-privilege users to infer folder visibility and ownership based on folder names, potentially accessing or interacting with other users' content. This affects all deployments using the vulnerable version where multiple users have accounts. The vulnerability stems from improper permission handling that was corrected with explicit ACLs in version 1.5.0.
💻 Affected Systems
- FileRise
📦 What is this software?
Filerise by Filerise
⚠️ Risk & Real-World Impact
Worst Case
Unauthorized users could access, modify, delete, or share sensitive files belonging to other users, leading to data breaches, data loss, or privilege escalation.
Likely Case
Users can see folder names matching their username and potentially access some content they shouldn't, leading to information disclosure and unauthorized file operations.
If Mitigated
With proper network segmentation and user education, impact is limited to internal information disclosure between authenticated users.
🎯 Exploit Status
Exploitation requires authenticated low-privilege access. Attackers simply need to browse folders or attempt operations on folders matching usernames.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: 1.5.0
Vendor Advisory: https://github.com/error311/FileRise/security/advisories/GHSA-jm96-2w52-5qjj
Restart Required: Yes
Instructions:
1. Backup your FileRise data and configuration. 2. Download FileRise version 1.5.0 from the official repository. 3. Replace the existing installation with the new version. 4. Restart the FileRise service or web server. 5. Verify ACLs are properly configured for all existing folders.
🔧 Temporary Workarounds
Disable multi-user mode
allConvert to single-user installation to eliminate the vulnerability
Modify configuration to allow only one user account
Restrict folder naming
allPrevent users from creating folders matching usernames
Implement server-side validation on folder creation
🧯 If You Can't Patch
- Implement strict network segmentation to isolate FileRise from sensitive systems
- Enable detailed audit logging and monitor for unauthorized folder access attempts
🔍 How to Verify
Check if Vulnerable:
Check FileRise version in admin panel or configuration files. If version is exactly 1.4.0 and multiple users exist, the system is vulnerable.Check Version:
Check the version.txt file or admin interface for version informationVerify Fix Applied:
After upgrading to 1.5.0, test that users cannot access folders they don't have explicit permissions for, regardless of folder names.📡 Detection & Monitoring
Log Indicators:
- Failed permission checks on folder operations
- Users accessing folders not explicitly shared with them
- Unusual pattern of folder listing requests
Network Indicators:
- Multiple failed authorization attempts followed by successful access
- Unusual file operations from low-privilege accounts
SIEM Query:
source="filerise" AND (event_type="folder_access" OR event_type="permission_denied") | stats count by user, folder_path