FileRise is a self-hosted web-based file manager with multi-file upload, editing, and batch…

Why it is Yellow

• CVSS 6.5 medium

References

• https://github.com/error311/FileRise/commit/cc1118923b522baff28dca05bdd79c27f984c68a
• https://github.com/error311/FileRise/releases/tag/v3.23.0
• https://github.com/error311/FileRise/security/advisories/GHSA-77m8-hm3q-mrr5

Original description

FileRise is a self-hosted web-based file manager with multi-file upload, editing, and batch operations. Prior to 3.23.0, FileRise permits an authenticated session with a valid CSRF token to disable TOTP without recent full reauthentication or to begin enrollment when the account currently has no TOTP secret. The enrollment endpoint returns 409 rather than directly overwriting an already configured secret, but it persists and activates a newly generated secret before a TOTP code verifies possession. An attacker controlling an existing authenticated session can therefore disable an existing second factor or enroll one after the account has no configured secret; this is not a direct overwrite of an active authenticator. This issue is fixed in version 3.23.0.