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