Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain valid public share token
-
DeliveryEnable/use subfolder browsing in share
-
ExploitFollow in-folder symlink to sibling directory
-
ExecutionList or download out-of-bounds files
-
ImpactDisclose files outside shared folder
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Symlink resolution safety
|
| Exploitation Conditions | Requires ALL of: (1) a public shared-folder link whose subfolder browsing is enabled; (2) a pre-existing symbolic link inside that shared folder pointing to a sibling directory under the upload root; (3) the local storage adapter (the fix only applies the real-path boundary check when $storage->isLocal() is true, indicating the symlink-following path is local-filesystem specific); and (4) possession of a valid share token. Exploitation is limited by High attack complexity - the attacker typically cannot create the required symlink themselves and depends on one already present - and the impact is confined to sibling directories under the upload root, not the whole filesystem. These factors make realistic risk materially lower than the unauthenticated network vector alone would suggest. |
| Impact | This is a medium-severity, low-priority issue in practice. The CVSS 3.1 vector (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N, base 4.8) signals network reachability and no authentication, but High attack complexity (AC:H) is the dominant limiting factor: exploitation depends on a symbolic link already existing inside the shared folder that points to a sibling directory under the upload root - a condition the share-token holder generally cannot create themselves in a default deployment. There is no EPSS score, no CISA KEV listing, and no public exploit identified at time of analysis, so there is no evidence of real-world exploitation. The commit diff confirms the root cause (symlink resolution without enforcing the original shared-folder real-path boundary, CWE-59) and confirms the fix in v3.15.0, so the technical claim is well substantiated. The PR:N in CVSS counts the share token as 'no privilege,' but note the description explicitly requires 'a valid share token' - so exploitation is gated on the attacker first possessing a legitimate share link, which narrows the realistic attacker population to those already granted share access or who can obtain a leaked token. Net: a genuine but constrained information-disclosure/limited-integrity flaw, not an urgent mass-exploitation threat. |
| Exploit ScenarioDerived | An attacker holding a valid public share link (with subfolder browsing enabled) to a FileRise folder that contains a symbolic link pointing to a sibling directory uses the shared-folder listing, direct download, or ZIP-creation feature to traverse the symlink and read files outside the folder that was actually shared. No account login is required beyond the share token, but the attack only succeeds where such a symlink already exists and the local storage adapter is in use. No public exploit identified at time of analysis; the fix commit is public. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Symbolic-link following in FileRise public shared-folder links (all versions prior to 3.15.0) allows an unauthenticated holder of a valid share token to read files outside the folder that was actually shared, confined to sibling directories under the upload root. Exploitation requires a pre-existing symlink inside the shared folder, subfolder browsing enabled on the share, and the local storage adapter, making the practical risk lower than the raw network vector suggests; no public exploit code was identified at time of analysis and the issue is not in CISA KEV. The vendor addressed it in version 3.15.0.
RemediationAI
Upgrade FileRise to version 3.15.0 or later, which is the vendor-released fix; the patch (commit f24af3f2a25cec092d19de93acbc215e74659a22, tagged v3.15.0) enforces the originally shared folder as the real-path boundary for shared-folder listing, direct download, ZIP creation, and upload targets, and preserves support for normal in-bound subfolders and files. Until upgrading, disable subfolder browsing on public shared-folder links so that only the share root is reachable, and revoke or rotate any share tokens exposed to untrusted parties, accepting that this reduces the functionality of the share. Note that the fix's boundary check is applied only when the local storage adapter is in use, so switching affected shares to a non-local storage adapter also removes the reachable code path, but this is a larger architectural change with its own operational trade-offs. Administrators should additionally verify that shared folders contain no symlinks pointing elsewhere under the upload root, since a pre-existing link is the precondition for exploitation, and audit file lists of public shares for unexpected sibling-directory content. Reference material: the GitHub advisory at https://github.com/error311/FileRise/security/advisories/GHSA-83rw-5ffw-p798 and release notes at https://github.com/error311/FileRise/releases/tag/v3.15.0.
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-59 (Improper Link Resolution Before File Access), a classic symlink-following boundary failure in a PHP application. FileRise's FolderModel resolved shared-folder subpaths with realpath() and validated them using a naive string-prefix check (strpos($real, $base) !== 0), which is unsafe because a sibling directory such as /upload/share-evil can share a string prefix with /upload/share, and because the resolved real path was not constrained to the originally shared folder root. The fix introduces an isPathInsideOrSame() helper that trims trailing directory separators and compares path components against a root prefix (root . DIRECTORY_SEPARATOR), and applies it in resolveFolderPath(), resolveFolderPathForAdapter(), resolveSharedFolderContext(), getSharedFileInfo(), listSharedFolderEntries() (with a new $shareRootRealPath parameter), and uploadToSharedFolder(). Notably the boundary check is gated on $storage->isLocal(), indicating the vulnerable symlink traversal is specific to the local filesystem storage adapter; listing, direct download, upload targets, and ZIP creation are all covered by the hardening. The affected code path is reachable only through tokenized public shares with subfolder browsing, per CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N, where PR:N confirms unauthenticated access and AC:H reflects attacker dependence on a pre-existing symlink.
Know when the next one hits your stack
- 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:H/PR:N/UI:N/S:U/C:L/I:L/A:N
Network-reachable share endpoint (AV:N) with no account needed (PR:N), but a pre-existing symlink precondition yields AC:H; read and limited write (upload targets) to out-of-bounds files give C:L/I:L, no availability impact.
Primary rating from Vendor (github).
CVSS VectorVendor: github
Lifecycle Timeline
1DescriptionCVE.org
FileRise is a self-hosted web-based file manager with multi-file upload, editing, and batch operations. Prior to 3.15.0, FileRise public shared-folder links with subfolder browsing enabled can follow a symbolic link inside the shared folder to a sibling directory under the upload root. An unauthenticated holder of a valid share token can use shared-folder listing, direct download, or ZIP creation to access files outside the folder that was actually shared. The flaw occurs because the affected shared-folder paths resolve symlinks without enforcing the original shared folder as the real-path boundary. This issue is fixed in version 3.15.0.
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.
EUVD-2026-101626
NVD
CVE.org
EPSS
Vulnrichment
GitHub
Exploit-DB