# CVE-2026-103977: FileRise TOTP bypass via session reset

Source: https://junglewise.ai/threats/cve-2026-103977-filerise-is-a-self-hosted-web-based-file-manager-with-multi-file  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-14. Updated: 2026-10-20  
License: CC BY 4.0 with a link back

CVE-2026-103977 · Severity: high · CVSS 8.1 · Published 2026-10-14

FileRise is a self-hosted web-based file manager. An attacker with a target user's password could bypass two-factor authentication (TOTP) by restarting the login process in a new session to reset the failed attempt counter, allowing unlimited guesses instead of the intended five attempts. This allows account takeover without a valid second-factor code.

Technologies: [Error311 FileRise](https://junglewise.ai/threats/technologies/filerise). Vendors: [Error311](https://junglewise.ai/threats/vendors/error311).

## Quick answers

**Is CVE-2026-103977 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-103977 being exploited in the wild.

**How severe is CVE-2026-103977?** High severity, with a CVSS score of 8.1, published 14 October 2026.

**Which products and versions are affected?** Error311 FileRise prior to 3.23.0.

**Is there a fix for CVE-2026-103977?** Yes: fixed in 3.23.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-103977 attacked?** It is attacked over the network.

**Am I affected by CVE-2026-103977?** Check whether you run Error311 FileRise at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in 3.23.0

## Technical details

The vulnerability exists in the TOTP verification handler, which stored failed attempt counts in the PHP session rather than as a durable account-wide limit. An attacker with valid credentials could initiate a new login session, resetting the attempt counter and bypassing the five-attempt rate limit. The fix in v3.23.0 implements persistent account-wide and source-wide attempt budgets that span all pending-login verification paths and cannot be reset by session restart.

## Affected products

- error311 FileRise prior to 3.23.0

## Timeline

- 2026-10-14: disclosed
- 2026-07-25: patched

## References

- [https://github.com/error311/FileRise/commit/cc1118923b522baff28dca05bdd79c27f984c68a](https://github.com/error311/FileRise/commit/cc1118923b522baff28dca05bdd79c27f984c68a)
- [https://github.com/error311/FileRise/releases/tag/v3.23.0](https://github.com/error311/FileRise/releases/tag/v3.23.0)

## Related threats

- [FileRise authentication bypass via proxy header spoofing](https://junglewise.ai/threats/cve-2026-57489-filerise-is-a-self-hosted-web-based-file-manager-with-multi-file)
- [FileRise path traversal in archive extraction via symlink](https://junglewise.ai/threats/cve-2026-104109-filerise-is-a-self-hosted-web-based-file-manager-with-multi-file)
- [FileRise missing CSRF enforcement for file creation](https://junglewise.ai/threats/cve-2026-54459-filerise-is-a-self-hosted-web-based-file-manager-with-multi-file)
- [error311 FileRise path traversal in shared-folder upload](https://junglewise.ai/threats/cve-2026-54414-error311-filerise-path-traversal-in-shared-folder-upload)
- [error311 FileRise TOTP bypass in totp_setup.php](https://junglewise.ai/threats/cve-2026-44460-error311-filerise-totp-bypass-in-totp-setup-php)