Severity by source
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Network vector with high complexity due to non-default proxy-auth configuration prerequisite; PR:L reflects required prior token possession; no availability impact identified.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Lifecycle Timeline
3DescriptionCVE.org
File Browser versions from 2.50.0 through 2.63.21 fail to validate JWT expiration when proxy authentication is configured with a non-default logout page. Attackers with a previously valid token can access protected routes and administrative endpoints indefinitely, and exchange expired tokens for fresh ones via the renewal endpoint.
AnalysisAI
File Browser versions 2.50.0 through 2.63.21 permit indefinite session persistence via expired JWT tokens when proxy authentication is configured with a non-default logout page, enabling an attacker who possesses any previously valid token to access protected routes and administrative endpoints beyond the token's expiration window. The authentication middleware intentionally waived JWT expiration under proxy-auth - since the proxy is expected to govern session lifetime - but failed to require the proxy to simultaneously assert the user's identity on each request, meaning a leaked or captured token could authenticate independently and indefinitely. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires three concurrent conditions: (1) File Browser must be configured to use proxy authentication (AuthMethod set to MethodProxyAuth); (2) the logout page must be configured to a non-default custom value (the vulnerable code path is triggered only when this non-default setting is detected); and (3) the attacker must possess a JWT token that was previously valid for the target instance - obtained through legitimate prior access, network capture, log exfiltration, or browser history. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 4.0 score of 7.6 reflects meaningful but conditionally constrained risk: AC:H and AT:P signal that exploitation requires the specific co-occurrence of proxy authentication enabled and a non-default logout page, neither of which is the default configuration. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker who previously authenticated to a File Browser instance - or who captured a JWT from network traffic, application logs, or a browser session - allows the token to expire naturally, then submits it directly to a protected API endpoint or the token renewal endpoint on a proxy-auth deployment with a non-default logout page. Because the pre-patch middleware waives expiration without validating the proxy identity header, the expired token is accepted, granting full access to protected files and administrative functions; the renewal endpoint can then be used to obtain a fresh, unexpired token, converting a time-limited exposure into persistent access. … |
| Remediation | The upstream fix is available as commit 72faf6dd3c85628e332d3e567124b86708ce2695 (https://github.com/filebrowser/filebrowser/commit/72faf6dd3c85628e332d3e567124b86708ce2695); a tagged patched release version has not been independently confirmed from the available data - consult the vendor advisory at https://github.com/filebrowser/filebrowser/security/advisories/GHSA-v3jv-rmh2-635j for the exact released version before upgrading. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, identify all File Browser deployments and determine which use proxy authentication with custom logout page configurations-these deployments require immediate attention. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
More in Filebrowser
View allUnauthorized file operations in File Browser before fix. PoC and patch available.
A cross-site scripting (XSS) vulnerability in FileBrowser before v2.23.0 allows an authenticated attacker to escalate pr
Path normalization bypass in Filebrowser prior to 2.57.1 allows authenticated users to circumvent file access restrictio
File Browser provides a file managing interface within a specified directory and it can be used to upload, delete, previ
File Browser provides a file managing interface within a specified directory and it can be used to upload, delete, previ
Arbitrary file deletion in filebrowser before 2.63.19 allows authenticated users holding only Create permission to delet
File Browser versions prior to 2.61.0 incorrectly set the filesystem root to a parent directory when generating public s
File Browser provides a file managing interface within a specified directory and it can be used to upload, delete, previ
File Browser provides a file managing interface within a specified directory and it can be used to upload, delete, previ
Filebrowser versions prior to 2.57.1 allow authenticated users to reset passwords without verifying the current password
Path traversal in FileBrowser Quantum (gtsteffaniak fork) versions prior to 1.3.2-stable, 1.4.0-beta, and 1.4.1-beta all
Filebrowser versions up to 2.55.0 contains a vulnerability that allows attackers to enumerate valid usernames by measuri
Same weakness CWE-613 – Insufficient Session Expiration
View allSame technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-57815
GHSA-32pr-94pq-34pj