# CVE-2026-103977: FileRise: Session-scoped TOTP rate limiting permits repeated verification attempts

> Attackers with valid primary credentials can bypass TOTP rate limits by resetting sessions, enabling brute-force attacks against two-factor authentication.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-4hfj-6478-5cv7

## What is CVE-2026-103977?

CVE-2026-103977 is a high-severity vulnerability in error311 FileRise, published on 14 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

FileRise is a self-hosted web-based file manager with multi-file upload, editing, and batch operations. Prior to 3.23.0, FileRise stores failed TOTP verification attempts in $_SESSION. An attacker who already possesses a target account's valid primary credential can restart the login workflow in a new session and restore the second-factor attempt allowance, permitting continued online TOTP guessing beyond the intended five-attempt limit. The pending-login TOTP handlers did not share a durable account-wide limit. This issue is fixed in version 3.23.0.

Weakness: CWE-841 (Improper Enforcement of Behavioral Workflow), CWE-307 (Improper Restriction of Excessive Authentication Attempts)

## Which versions are affected by CVE-2026-103977?


## How do I fix CVE-2026-103977?

No fix has been published for CVE-2026-103977 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-103977 being exploited?

There is no known exploitation of CVE-2026-103977 in the wild and no public exploit code.

Public exploit code:

- Session-scoped TOTP rate limiting permits repeated verification attempts (github_poc): https://github.com/pervinzahidli/CVE-2026-103977

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-103977 and fix it if it is affected.

What it is: CVE-2026-103977 is a high-severity vulnerability in error311 FileRise, published on 14 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-103977 in the wild and no public exploit code.

Affected product: error311 FileRise. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-103977/ (Markdown: https://insights.sbomify.com/CVE-2026-103977/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-103977
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-103977
- OSV: https://osv.dev/vulnerability/CVE-2026-103977

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-103977/
Summaries are generated and may contain mistakes; the official description above is the record.