CriticalCVE-2025-12480

    Gladinet Triofox Improper Access Control Vulnerability (CVE-2025-12480)

    Published Last modified In CISA KEV since Sources: CVE.org, pwn.watch

    Share

    What is affected, what to do

    Triofox versions prior to 16.7.10368.56560, are vulnerable to an Improper Access Control flaw that allows access to initial setup pages even after setup is complete.

    The vulnerability is being actively exploited; treat it as a priority. Update TrioFox to version 16.7.10368.56560. Immediate actions, mitigation and detection rules are in the runbook below.

    Affected
    • TrioFox lt *..16.7.10368.56560
    Fixed in
    • TrioFox 16.7.10368.56560

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

    Metrics

    9.1

    Priority

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

    Source: NVD, CVSS v3

    9.1

    CVSS v3

    Severity Critical on the scale from 0 to 10.

    Source: CVE.org, pwn.watch

    95.8 %

    EPSS score

    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.

    Source: FIRST EPSS, percentile 99.87

    Show all metrics
    Severity
    Critical
    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
    237.20 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
    actively exploitedSource: VulnCheck KEV (opens in a new tab) How we classify
    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
    9.1 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
    9.1
    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
    95.8 %
    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.
    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
    99.87
    Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
    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
    Actively exploited
    Published
    In CISA KEV since

    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
    CISA assessment (SSVC)
    Exploitation: active · automatable · Technical impact: total
    Source: CISA Vulnrichment, as of 11 November 2025
    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-284

    Response and mitigation

    Why act now?

    Prioritisation rationale

    The flaw is reachable over the network without authentication or user interaction. It hands an attacker administrative control of the file-sharing platform. Combined with abuse of the AV scanner setting, that becomes SYSTEM-level code execution. Exploitation likelihood is among the highest of any CVE, and public write-ups describe a simple, reproducible attack chain. Typical targets are Internet-facing Triofox instances that act as remote-access gateways to internal file servers. CISA does not flag known ransomware use. Even so, the direct path to corporate data and an internal foothold justifies treating Internet-exposed instances as critical, with action required today. Internal-only deployments should be patched within days.

    1. Runbook step 1

      Immediate response (0-24 h)

      • Patch now: Upgrade every Triofox server to version 16.7.10368.56560 or later. Confirm the running version in the management console and reconcile it against your asset inventory, including test and forgotten instances.
      • Cut exposure: Until patched, block Internet access to the Triofox web interface at the perimeter firewall or reverse proxy. Allow access only through VPN or an IP allowlist.
      • Audit admin accounts: Look for unknown or recently created administrator accounts in Triofox native users and admin roles. Public analyses show attackers using the setup pages to create new admin accounts. Disable rogue accounts, but preserve them as evidence first.
      • Check for configuration tampering: Inspect the antivirus scanner path in Triofox settings. It must point to your legitimate AV engine, not to a script (.bat/.ps1/.cmd) or an unknown binary. If it has been altered, treat the host as compromised and isolate it.
      • Rotate credentials: If you find signs of compromise, rotate all Triofox admin passwords and the connected service accounts (AD/LDAP binds, cloud storage keys, database credentials). Also rotate local admin passwords on the host.
      • Preserve evidence: Capture IIS/web logs, Triofox application logs, Windows event logs and a memory image before you patch or reboot.

    2. Runbook step 2

      Mitigation layers

      • Network segmentation: Place Triofox in a DMZ or a dedicated segment. Restrict egress to the storage endpoints it actually needs. Block outbound SSH, RDP and remote-access services (AnyDesk, ScreenConnect, etc.).
      • Reverse proxy/WAF rule: Drop externally sourced requests whose Host header is localhost or 127.0.0.1, because the publicly documented bypass relies on a Host header check. Also deny external access to setup and management paths (e.g. AdminDatabase.aspx, AdminAccount.aspx, /management/).
      • Endpoint hardening: Use WDAC/AppLocker to stop Triofox processes from spawning cmd.exe, powershell.exe or unsigned binaries from writable paths. Switch the EDR policy for this host to block mode.
      • IAM / least privilege: Where possible, run the Triofox service under a low-privileged service account rather than SYSTEM. Require MFA for console admin access.
      • Configuration monitoring: Put Triofox configuration files and registry keys under file integrity monitoring so that any change to the AV scanner path raises an alert.

    3. Runbook step 3

      Detection rules

      • Web server logs (IIS W3C): Watch for external source IPs hitting setup pages, for example cs-uri-stem ending in AdminDatabase.aspx or AdminAccount.aspx. If header logging is enabled, flag cs-host=localhost from non-loopback clients. SPL: index=iis (cs_uri_stem="*AdminDatabase.aspx" OR cs_uri_stem="*AdminAccount.aspx") NOT c_ip IN ("127.0.0.1","::1")
      • Sysmon EID 1 / EDR process ancestry: Alert when Triofox processes (path *\Triofox\*) spawn cmd.exe or powershell.exe, or execute .bat files. KQL: DeviceProcessEvents | where InitiatingProcessFolderPath has "Triofox" and FileName in~ ("cmd.exe","powershell.exe")
      • Post-exploitation tooling: Watch for remote-access and tunnelling tools (AnyDesk, Zoho UEMS/Assist, plink.exe, putty.exe) appearing on the Triofox host. Relevant sources are Sysmon EID 1 and 11 and Windows EID 7045 (new service).
      • Network telemetry (Zeek/Suricata): Flag outbound SSH from the Triofox server, especially on unusual ports (e.g. 433), and reverse tunnels to RDP 3389. Zeek: conn.log where service=="ssh" and id.orig_h is the Triofox IP.
      • Account telemetry: Look for new Triofox admin accounts in the application logs. On the host, correlate Windows EID 4720/4732 (local account created or added to Administrators) with setup page access.

    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
    Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
    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
    Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
    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

    Triofox versions prior to 16.7.10368.56560, are vulnerable to an Improper Access Control flaw that allows access to initial setup pages even after setup is complete.

    Source: cvelistv5, pwn.watch, NVD (NIST), CISA KEV Catalog, CVE.org (MITRE)

    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
    TrioFoxTrioFox
    • < 16.7.10368.56560
    • 16.7.10368.56560
    gladinettriofox
    • < 16.7.10368.56560
    • 16.7.10368.56560

    Vendors and products

    Weakness classes (CWE)

    • CWE-284Improper Access Control

      Pillar

      The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

      Entry at MITRE CWE-284

    Public exploit references

    Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

    Public exploit references
    CISA KEV CatalogCISA Known Exploited Vulnerability (opens in a new tab)cisa.govactively exploited

    References & sources

    • github.commandiant/Vulnerability-Disclosures/blob/master/2025/MNDT-2025-0…Third-party advisory, Third-party advisory
    • triofox.comProduct, Product
    • access.triofox.comreleases_historyRelease notes, Release notes
    • cloud.google.comblog/topics/threat-intelligence/triofox-vulnerability-cve-2025-…Third-party advisory, Exploit, Third-party advisory
    • cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2025-12480government-resource, US government resource
    • pwn.watchpwn.watch: Gladinet Triofox: Triofox Improper Access Control Vulnerabilitypwn-watch
    • access.triofox.comGladinet advisory: Gladinet Triofoxpwn-watch
    • NVD (NIST)NVD: CVE-2025-12480pwn-watch
    • cisa.govCISA Known Exploited Vulnerabilities Catalogpwn-watch

    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).

    One NVD translation into another language is hidden.

    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-2025-12480
    <a href="https://intel.neosec.eu/en/cve/CVE-2025-12480"><img src="https://intel.neosec.eu/badge/cve/CVE-2025-12480.svg?lang=en" alt="CVE-2025-12480 – NEOSEC Intel" height="20"></a>