Skip to content

← Actionable
Medium, CVSS 5.9amended

FileGator: Missing authorization in POST /upload allows cross-user read and deletion of temporary files

CVE-2026-94619GHSA-44r8-3p76-84mw

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (filegator/filegator 7.15.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.9 · CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:L
EPSS
  • CVE-2026-94619: 0.17% estimated exploitation activity in the next 30 days; percentile 6.57 (FIRST EPSS, 2026-11-10). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary `POST /upload` uses the request-supplied `resumableFilename` directly as a key into the shared temporary directory, without the character filter it applies to `resumableIdentifier` and without namespacing it per user. A valid user holding the `upload` permission can read any file in that directory into their own home directory, append to it, and delete it. This reproduces the cross-user batch-archive disclosure of GHSA-f74m-x83r-c4v4 through a different route — it still works with the fix for that advisory (PR #597) applied — and additionally allows deleting the login rate-limit lockfile. Reported with explicit preconditions and bounded impact, as before: the primitive is confined to the temporary directory, not the whole filesystem.

Details - `backend/Controllers/UploadController.php:61` — `$file_name = $request->input('resumableFilename', 'file')` is not passed through the `preg_replace('/[^0-9a-zA-Z_]/', '', ...)` that line 66 applies to `resumableIdentifier`. -…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from osv record GHSA-44r8-3p76-84mw

  2. Revision 1 · created ·

    Published from ghsa record GHSA-44r8-3p76-84mw

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-94619

Advisory: FileGator: Missing authorization in POST /upload allows cross-user read and deletion of temporary files
IDs: CVE-2026-94619, GHSA-44r8-3p76-84mw
Record: https://patchnext.com/advisories/cve-2026-94619 (revision 2, source checked 10 Nov 2026, 06:35 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: filegator/filegator 7.15.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist filegator/filegator: affected < 7.15.0; fixed in 7.15.0

## Suggested inspection (read-only)
- Packagist filegator/filegator: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on filegator/filegator.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-44r8-3p76-84mw (GitHub-reviewed advisory GHSA-44r8-3p76-84mw lists affected ranges: Packagist filegator/filegator >=0 <=7.14.4)
- Verified: https://osv.dev/vulnerability/GHSA-44r8-3p76-84mw (OSV record GHSA-44r8-3p76-84mw lists affected ranges: Packagist filegator/filegator >=0 <7.15.0 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…