CVE-2026-104110: FileRise: Unauthenticated disclosure of internal folder path, client email, and upload policy for FileRise Pro client portals via /api/pro/portals/get.php
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-11 15:49 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
FileRise is a self-hosted web-based file manager with multi-file upload, editing, and batch operations. Prior to 3.24.0, FileRise Pro /api/pro/portals/get.php returns a configured client portal’s full internal record to an unauthenticated caller who knows or guesses the portal slug. The response includes the internal storage folder path, client contact email, form settings, and upload-policy details, while the separate publicMeta.php endpoint intentionally exposes only curated branding data. Exploitation requires the Pro add-on and at least one configured portal. This issue is fixed in version 3.24.0.
Description quoted from the CVE record (assigned by GitHub_M, published 2026-10-14).
Weakness: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor; CWE-306: Missing Authentication for Critical Function
How it can be exploited
Exploitable over the network with low attack complexity needing no privileges and no user interaction. Impact: confidentiality low, integrity none, availability none. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
CISA assessment (SSVC): CISA assesses that a public proof of concept exists. Automatable: yes. Technical impact: partial.
Public exploit evidence (Exploit Observer)
Exploit Observer found 4 code repositories naming this CVE.
Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.
See all 6 references on Exploit Observer
Live scores
- EPSS
- 0.003
low predicted chance of attack - VEDAS
- 0.987
strong exploit evidence - On CISA KEV
- Not listed
- Detection rule
- Suricata
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| error311 FileRise | version < 3.24.0 | Not stated |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
How to fix it
No fixed version or vendor advisory is listed in the CVE record yet. Watch the vendor’s security page.
How to detect it
Suricata rules (network detection)
1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-104110 FileRise - Information Disclosure. Add them to your Suricata rule set and reload.
Show the rules
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-104110 FileRise - Information Disclosure"; flow:established,to_server; http.method; content:"GET"; http.uri; content:"/api/pro/portals/get.php"; nocase; fast_pattern; content:"slug="; nocase; classtype:web-application-attack; reference:cve,CVE-2026-104110; reference:url,https://www.exploit.observer/?keyword=CVE-2026-104110&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=filerise&match=exact; sid:1080402; rev:1;)
CVE-2026-104110.rules on GitHub
References
Other references
- https://github.com/error311/FileRise/security/advisories/GHSA-m49m-9v4m-w2rq (x_refsource_CONFIRM)
- https://github.com/error311/FileRise/commit/1bf1f44d221398dcf6484520d0905e1f4bf319c7 (x_refsource_MISC)
- https://github.com/error311/FileRise/releases/tag/v3.24.0 (x_refsource_MISC)
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.
Supporting partners
