MediumCVE-2026-94618

    FileGator: Use of Insufficiently Random Values (CVE-2026-94618)

    Published Last modified Sources: Hersteller, CVE.org

    Share

    What is affected, what to do

    Update FileGator to version 7.15.0.

    Affected
    • FileGator lt *..7.15.0
    Fixed in
    • FileGator 7.15.0

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    5.4

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: Vendor (CNA), CVSS v3

    5.4

    CVSS v3

    Severity Medium on the scale from 0 to 10.

    Source: Hersteller, CVE.org

    0.2 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 8.6

    Show all metrics
    Severity
    Medium
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    57.59 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    5.4 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    5.4
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    0.2 %
    Low — model estimates < 1% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    8.6
    Low — this CVE sits in the lower 10% of all CVEs scored today.
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-330, CWE-862

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    Summary

    GET /batchdownload streams a batch ZIP to any requester who supplies its uniqid, without checking that the current user/session created it. In deployments where users have separate home directories, a valid low-privileged user who obtains an active archive id can download another user's batch archive, disclosing files the per-user boundary otherwise protects. Reported with explicit preconditions and bounded impact — not a universal "any user steals any file" issue.

    Details

    The archive id is generated with plain uniqid() and no ownership metadata is bound to it before streaming.

    • backend/Services/Archiver/Adapters/ZipArchiver.php:44 — createArchive() uses plain uniqid().
    • backend/Controllers/DownloadController.php:144-145 — batchDownloadStart() reads the tmpfs file by the request-supplied uniqid after only a charset preg_replace().
    • backend/Controllers/DownloadController.php:158 — the tmpfs archive is removed only after streaming.
    • backend/Controllers/routes.php:207-226 — both batch endpoints are exposed to normal roles with read, download, batchdownload.

    No user id, session id, home directory, or creator check is applied before streaming. The code path is unchanged since commit 3f03a40 (2022-05-31) and is present in the latest release v7.14.3.

    PoC

    Preconditions: a multi-user deployment with distinct per-user homedirs (set per-user in users.json, or private_repos => true on the WordPress/LDAP adapter). The shipped sample config (admin/guest both at /, guest with no perms) does not create this boundary on its own. Attacker is a valid user with read, download, batchdownload.

    1. User John (homedir /john) creates secret.txt, signs in, and creates a batch archive via POST /batchdownload. The JSON response returns the archive uniqid.
    2. User Jane (homedir /jane, with batchdownload) signs in normally.
    3. Jane's direct GET /download of /secret.txt returns 302 — the normal home-directory boundary blocks the file.
    4. Jane sends GET /batchdownload?uniqid=<John's id> and receives a valid ZIP containing secret.txt with John's content.

    A PHPUnit proof with two real sessions reproduces this end to end (OK, 3 tests / 29 assertions), plus a lifecycle test (OK, 2 tests / 9 assertions). Full test files, run logs, and a real Apache access-log replay demo are available on request.

    Lifetime / acquisition: a normal completed download removes the archive at the end of streaming, limiting the window. An aborted/failed download leaves the archive in tmpfs (cleanup never reached). The frontend issues the download as a top-level navigation (window.open('.../batchdownload&uniqid='+ret.uniqid, '_blank')), so the id appears in standard web access logs. That access-log path only adds meaningful impact when log visibility is decoupled from host filesystem access (e.g. a log-aggregation/shared-hosting/downstream-sink reader) and the archive is still alive; if the reader is ops/root on the same host they can already read the storage tree directly. The uniqid() token is timestamp-derived (1,000,000-value space per known second) — included to justify a CSPRNG, not presented as a practical universal brute force.

    Impact

    Missing authorization (CWE-862) on a temporary download object, leading to cross-user file disclosure across the per-user home-directory boundary in configured multi-user deployments. Secondary effect: a successful replay deletes the victim's pending archive (the GET removes the tmpfs file after streaming), denying the victim their own download if not yet consumed.

    Remediation: generate ids with bin2hex(random_bytes(32)); store creator user/session + home dir + expiry per archive id; verify the requester matches before streaming and return 403/404 on mismatch or unknown/expired id; delete metadata with the tmpfs file.

    Source: GitHub Security Advisories, cvelistv5, NVD (NIST)

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    filegatorfilegator
    • < 7.15.0
    • 7.15.0
    composerfilegator/filegator
    • <= 7.14.4
    • 7.15.0

    Vendors and products

    Weakness classes (CWE)

    • CWE-330Use of Insufficiently Random Values

      Class

      The product uses insufficiently random numbers or values in a security context that depends on unpredictable numbers.

      Entry at MITRE CWE-330

    • CWE-862Missing Authorization

      Class

      The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

      Entry at MITRE CWE-862

    References & sources

    • github.comfilegator/filegator/commit/638737e560cbf20cbeb5da4e4e6c974f8a08…x_refsource_MISC
    • github.comfilegator/filegator/pull/597x_refsource_MISC
    • github.comfilegator/filegator/releases/tag/v7.15.0x_refsource_MISC
    • github.comfilegator/filegator/security/advisories/GHSA-f74m-x83r-c4v4x_refsource_CONFIRM

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. ReceivedGitHub

      CVSS V3.1: AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:N/A:L

      Weakness type: CWE-330, CWE-862

      Description added or changed

      Show 9 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Descriptionadded
      —
      FileGator is a multi-user file manager. Prior to 7.15.0, GET /batchdownload in backend/Controllers/DownloadController.php uses batchDownloadStart() to stream a shared temporary archive selected by the request-supplied uniqid without checking that the current session created it. In deployments with distinct per-user home directories, a valid user with read, download, and batchdownload permissions who obtains another user's active archive id can cross that boundary and retrieve the victim's batch archive. The archive lifetime and id-acquisition requirement limit exploitation, but a successful replay also deletes the victim's pending archive. This issue is fixed in version 7.15.0.
      CVSSadded
      —
      AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:N/A:L
      Weakness type (CWE)added
      —
      CWE-330
      Weakness type (CWE)added
      —
      CWE-862
      Affected versions (publisher)added
      —
      New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/94xxx/CVE-2026-94618.json">CVE-2026-94618</a>
      Referenceadded
      —
      https://github.com/filegator/filegator/commit/638737e560cbf20cbeb5da4e4e6c974f8a080531
      Referenceadded
      —
      https://github.com/filegator/filegator/pull/597
      Referenceadded
      —
      https://github.com/filegator/filegator/releases/tag/v7.15.0
      Referenceadded
      —
      https://github.com/filegator/filegator/security/advisories/GHSA-f74m-x83r-c4v4

      Source identifier: security-advisories@github.com

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-94618
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-94618"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-94618.svg?lang=en" alt="CVE-2026-94618 – NEOSEC Intel" height="20"></a>