Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate with stolen primary password
-
DeliverySubmit TOTP guesses to five-attempt limit
-
ExploitRestart login in fresh session
-
ExecutionResume online brute-forcing of TOTP
-
ImpactComplete 2FA and access file manager account
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Brute-force prevention, rate limiting
|
| Exploitation Conditions | Exploitation requires that the attacker already possess a valid PRIMARY credential (username + password) for a target FileRise account that has TOTP two-factor authentication enabled - this is the hard precondition and the main limiting factor. Given that, the attacker abuses the pending-login TOTP handlers, which store failed verification counts only in $_SESSION rather than in a durable account-wide/source-wide budget: starting a new session (or changing client source address) restores the second-factor attempt allowance, enabling TOTP guessing beyond the intended five-attempt cap. Limiting factors beyond the credential requirement: success is still a probabilistic online guess against a time-limited rotating code, and deployments without TOTP enabled are unaffected by this specific bypass. Affected versions are all releases prior to 3.23.0. |
| Impact | This is a genuine but conditional priority, not a trivial high-CVSS inflation. The CWE-307 flaw lets a session/source reset bypass the intended five-attempt TOTP limit, defeating the rate-limiting that makes a 6-digit second factor brute-force-resistant. The provided CVSS:3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N, 8.1) is internally consistent with the description: PR:L correctly reflects that the attacker must ALREADY hold the victim's valid primary credential - this is a 2FA-defeat flaw, not a pre-auth takeover, which meaningfully narrows the real-world attacker set. No EPSS score, CISA KEV listing, POC, or SSVC decision data were supplied, so automatability and exploitation-maturity signals cannot be weighed; absence of these is not evidence of safety but does mean there is no indication of active exploitation. The practical caveat: even with the limit removed, brute-forcing a TOTP code is a probabilistic online-guessing exercise against a rotating ~1,000,000-value space with ~30s time steps, so AC:L is arguably optimistic - real success still requires sustained guessing and the current time window, which may warrant AC:H. Priority should therefore be driven by exposure of compromised/weak primary passwords rather than by the 8.1 alone. |
| Exploit ScenarioDerived | An attacker who has phished or reused a FileRise user's primary password is stopped at the TOTP prompt after five wrong guesses. They simply open a fresh session (or change client address), which the pending-login handlers treat as a new attempt budget, and resume online guessing of the 6-digit code until they land a valid one, gaining full access to the victim's file manager. No public exploit code was identified at time of analysis, but the bypass requires only repeating the normal login flow. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Online second-factor guessing against FileRise releases prior to 3.23.0 is permitted well beyond the intended limit because failed TOTP verification attempts are recorded only in the PHP session rather than in a durable account-wide budget. An attacker who already possesses a valid primary credential (username plus password) for an account with TOTP enabled can abandon the pending login, start a fresh session, or change source address to restore the five-attempt allowance and continue guessing time-based codes indefinitely. Exploitation therefore has a hard precondition - the primary credential - and each guess remains a probabilistic online attempt against a rotating code, but a successful guess yields full account compromise; the vendor addressed the flaw in v3.23.0 and no public exploit code has been identified at time of analysis.
RemediationAI
Upgrade to FileRise v3.23.0, which is the vendor-released patch and contains the persistent account-wide and source-wide TOTP attempt budgets plus atomic time-step claiming (release notes: https://github.com/error311/FileRise/releases/tag/v3.23.0; advisory: https://github.com/error311/FileRise/security/advisories/GHSA-4hfj-6478-5cv7; upstream fix commit: cc1118923b522baff28dca05bdd79c27f984c68a). If immediate upgrade is not possible, treat the primary credential as the true security boundary: rotate passwords for all TOTP-enabled accounts, remove or disable unused accounts so fewer valid primary credentials exist to pair with the TOTP guess, and add an edge rate limit keyed on the authenticated username as well as the client IP so that resetting a session cookie cannot reset the external limiter - the trade-off is that aggressive per-IP throttling can lock out legitimate users behind shared NAT, and aggregate counting across all requests may interfere with the bulk file-upload and batch operations FileRise is designed for. Administrators can also verify no anomalous TOTP failures are occurring by monitoring authentication logs for repeated second-factor submissions across multiple sessions or source addresses, and should consider temporarily disabling TOTP for accounts where the primary credential cannot be rotated, though this reduces overall account protection. Because exploitation requires a valid primary credential, prioritizing password hygiene, disabling dormant accounts, and enforcing strong unique passwords materially lowers risk until the v3.23.0 upgrade is applied.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-307 (Improper Restriction of Excessive Authentication Attempts) in FileRise's pending-login TOTP verification flow. FileRise is a self-hosted, PHP-based web file manager (CPE cpe:2.3:a:error311:filerise:*:*:*:*:*:*:*:*), and prior to 3.23.0 the failed-attempt counter for TOTP submissions lived in $_SESSION, so the limiter was scoped to a single session object rather than to the account. Any action that produces a new session or a new apparent source - restarting the login workflow, discarding the session cookie, or originating from a different client address - reinitialized the counter to zero, and the pending-login handlers had no shared, durable account-wide or source-wide budget to fall back on. The v3.23.0 commit (cc1118923b522baff28dca05bdd79c27f984c68a) restructures this so verification enforces persistent account-wide and source-wide attempt budgets across all pending-login paths, claims accepted TOTP time steps atomically per account and authenticator secret to stop replay of a still-valid code, clears the account budget on success without penalizing ordinary logins from shared networks, and requires a full authentication no older than five minutes before TOTP enrollment, disablement, or recovery-code rotation can be changed. The independent assessment scores this as AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N, treating the pre-existing primary credential plus the probabilistic online guess as the principal constraints, rather than the higher base score originally published.
Know when Filerise gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Attacker must hold the victim's primary credential (PR:L) and still win a probabilistic online TOTP guess within rotating time windows (AC:H); full account access yields C:H/I:H, no availability impact.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
2DescriptionCVE.org
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.
Technical POC Analysis
CWE-307 (Improper Restriction of Excessive Authentication Attempts), with the advisory also listing CWE-841 (Improper Enforcement of Behavioral Workflow).
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
FileRise releases prior to 3.23.0 accept far more than the intended five second-factor guesses per account, because failed TOTP attempts are tracked against the PHP session rather than the account itself, so an attacker who already holds a valid username and password can restore the attempt allowance simply by starting a new session or changing source address and keep guessing. A successful guess completes a full takeover of a TOTP-protected account, exposing that identity's files, shares, and any administrative reach; no public exploit code has been identified at time of analysis. Leadership should care because the second factor expected to contain stolen-credential attacks is unreliable in this product, and remediation requires a version upgrade rather than a configuration tweak.
Apply vendor patch (upgrade FileRise to 3.23.0 or later, the version in which the vendor addressed the flaw; the advisory patch field lists no patch as available at time of analysis). Until the upgrade is verified, enforce per-account rate limiting or lockout for failed TOTP submissions at the reverse proxy, WAF, or identity layer; alert on repeated second-factor failures spanning sessions or source addresses; and rotate credentials for accounts with TOTP enabled.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Malicious file upload attacks exploit insufficient validation when web applications accept user-provided files.
Unauthenticated directory traversal in FileRise prior to version 3.3.0 allows remote attackers to read arbitrary files f
Unauthenticated administrator account takeover in FileRise before 3.16.0 is possible via a path traversal flaw in the sh
FileRise versions before 3.3.0 contain an HTML injection vulnerability that allows authenticated users to manipulate the
FileRise is a self-hosted web-based file manager with multi-file upload, editing, and batch operations. Prior to 2.2.3,
File overwrite in FileRise prior to 3.18.0 allows an unauthenticated visitor who holds a valid upload-enabled shared-fol
FileRise, a self-hosted web file manager and WebDAV server, contains a critical hardcoded encryption key vulnerability i
Multi-factor authentication bypass in FileRise WebDAV prior to 3.16.0 allows an attacker who already holds a valid usern
FileRise, a self-hosted web file manager and WebDAV server, contains a path traversal vulnerability in its Resumable.js
Authentication bypass in FileRise versions before 3.23.0 lets a remote attacker log in as an existing local account - in
Authentication bypass in FileRise (CWE-290) lets unauthenticated remote attackers impersonate any account - including an
FileRise 1.4.0 exposes folder visibility and ownership decisions to authenticated low-privilege users because a regressi
Low-privilege users of FileRise versions prior to 1.4.0 can view, delete, or modify files owned by other users because t
EUVD-2026-101685
NVD
CVE.org
EPSS
GitHub
Exploit-DB