CVE-2026-25231

7.5 HIGH

📋 TL;DR

FileRise versions before 3.3.0 have an unauthenticated file read vulnerability where anyone can access files in the /uploads directory without authentication by guessing or knowing file paths. This affects all users running vulnerable FileRise instances, potentially exposing sensitive uploaded files.

💻 Affected Systems

Products:
  • FileRise
Versions: All versions prior to 3.3.0
Operating Systems: All platforms running FileRise
Default Config Vulnerable: ⚠️ Yes
Notes: Affects all installations with the default /uploads directory configuration.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete exposure of all files uploaded to the vulnerable directory, including sensitive documents, credentials, or personal data, leading to data breaches and privacy violations.

🟠

Likely Case

Exposure of some uploaded files containing sensitive information, potentially leading to data leaks and privacy issues.

🟢

If Mitigated

No data exposure if proper access controls are implemented or the system is not internet-facing.

🌐 Internet-Facing: HIGH - Any internet user can potentially access sensitive files without authentication.
🏢 Internal Only: MEDIUM - Internal users could still access files they shouldn't, but attack surface is reduced.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Exploitation requires guessing or discovering file paths, but no authentication is needed.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 3.3.0

Vendor Advisory: https://github.com/error311/FileRise/security/advisories/GHSA-hv99-77cw-hvpr

Restart Required: Yes

Instructions:

1. Backup your FileRise data and configuration. 2. Download FileRise 3.3.0 from the official releases page. 3. Replace the existing installation with the new version. 4. Restart the FileRise service.

🔧 Temporary Workarounds

Restrict access to /uploads directory

all

Configure web server or application firewall to block unauthenticated access to the /uploads directory

# Example for nginx: location /uploads { deny all; }
# Example for Apache: <Directory /path/to/uploads> Require all denied </Directory>

Move uploads directory outside web root

all

Configure FileRise to store uploads in a directory not accessible via web server

# Edit FileRise configuration to change upload directory path

🧯 If You Can't Patch

  • Implement strict network access controls to limit who can reach the FileRise instance
  • Monitor access logs to the /uploads directory for unauthorized access attempts

🔍 How to Verify

Check if Vulnerable:

Attempt to access a known file in the /uploads directory without authentication. If accessible, the system is vulnerable.

Check Version:

Check FileRise version in web interface or configuration files

Verify Fix Applied:

After patching, attempt to access files in /uploads directory without authentication. Access should be denied.

📡 Detection & Monitoring

Log Indicators:

  • HTTP 200 responses to /uploads/* paths from unauthenticated users
  • Unusual access patterns to upload directory

Network Indicators:

  • Unusual volume of requests to /uploads paths
  • Requests to /uploads from unexpected IP addresses

SIEM Query:

source="webserver.log" AND uri_path="/uploads/*" AND http_status=200 AND NOT authenticated_user=*

🔗 References

📤 Share & Export