FileGator: Missing authorization in POST /upload allows cross-user read and deletion of temporary files
- Exploited
- No known exploitation
- Fix
- Fixed in 7.15.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 7.15.0.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 9/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
FileGator, a multi-user file manager, has a missing authorization flaw in its upload handling that lets a logged-in user with upload permission read, modify, or delete other users' temporary files, such as pending archives. An attacker can reach it remotely over the network with low-privilege login, but the attack also requires some user interaction.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
FileGator is a multi-user file manager. Prior to 7.15.0, POST /upload in backend/Controllers/UploadController.php uses the request-supplied resumableFilename as an unnamespaced key in shared temporary storage. In a multi-user deployment configured with distinct per-user home directories, a low-privileged user with upload permission can set resumableTotalChunks and resumableTotalSize to zero so the assembly loop writes no data, after which the handler reads a pre-existing temporary file with that name, stores it in the attacker's home directory, and removes it. The same filename path can append data when chunks are supplied, allowing disclosure, modification, or deletion of another user's transient object, including a pending archive or the login rate-limit lockfile, while Tmpfs path sanitization limits the primitive to the temporary directory. This issue is fixed in version 7.15.0.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.9/10CVSS 5.9
- No patch0/5No signal
What would change the score
- Would score about 64 if added to CISA KEV
- Would score about 59 if CISA's SSVC rates exploitation active
- Would score about 28 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 7.15.0.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- filegator filegator
fixed in 7.15.0
Evidence 4
- Advisory
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-94619
Is CVE-2026-94619 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-94619?
filegator: before 7.15.0.Source: cve.now feed data
How do I fix CVE-2026-94619?
Upgrade to a fixed version: 7.15.0.Source: cve.now feed data