{"schemaVersion":1,"url":"https://cve.openhack.com/cve/CVE-2025-62509","id":"CVE-2025-62509","title":"FileRise improper ownership/permission validation allowed cross-tenant file operations","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 u","descriptionLong":"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.","published":"2025-10-20T17:38:49.999Z","updated":"2026-10-28T02:31:14.795842794Z","reserved":"2025-10-15T15:03:28.133Z","status":"Analyzed","rejected":false,"assigner":"GitHub_M","metric":{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","rating":"high","source":"GitHub_M"},"metrics":[{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","rating":"high","source":"GitHub_M"},{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","rating":"high","source":"github.com"},{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","rating":"high","source":"OSV"}],"rating":"high","products":["error311 FileRise"],"affectedProducts":[{"vendor":"error311","product":"FileRise","defaultStatus":null,"versions":[{"version":"< 1.4.0","status":"affected"}],"platforms":[]}],"packages":[],"cwes":["CWE-280","CWE-284"],"aliases":["GHSA-6p87-q9rh-95wh"],"references":[{"url":"https://github.com/error311/FileRise/security/advisories/GHSA-6p87-q9rh-95wh","tags":["x_refsource_CONFIRM","Vendor Advisory","advisory"]},{"url":"https://github.com/error311/FileRise/issues/53","tags":["x_refsource_MISC","Issue Tracking","report"]},{"url":"https://github.com/error311/FileRise/commit/25ce6a76beb60950359c0304765ad91a8aff8ad8","tags":["x_refsource_MISC","Patch","fix"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/62xxx/CVE-2025-62509.json","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-62509","tags":["advisory"]}],"patchReferenced":true,"fixAvailable":true,"exploitReferenced":false,"kev":false,"kevAdded":null,"kevDue":null,"kevEntry":null,"ssvc":{"exploitation":"none","automatable":"no","technicalImpact":"partial"},"epss":0.00313,"epssPercentile":0.24709,"sources":[{"name":"CVE List","url":"https://www.cve.org/CVERecord?id=CVE-2025-62509","ok":true},{"name":"NVD","url":"https://nvd.nist.gov/vuln/detail/CVE-2025-62509","ok":true,"note":"Analyzed"},{"name":"OSV","url":"https://osv.dev/vulnerability/CVE-2025-62509","ok":true,"note":"0 packages"},{"name":"CISA KEV","url":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","ok":true,"note":"not listed"},{"name":"EPSS","url":"https://api.first.org/data/v1/epss?cve=CVE-2025-62509","ok":true,"note":"scored 2026-11-19"}],"aiTitle":false,"tech":[],"critical":[],"attention":null}