# CVE-2025-11371: Gladinet CentreStack and Triofox Files or Directories Accessible to External Parties

> Unauthenticated attackers can read system files via local file inclusion in Gladinet CentreStack and TrioFox, requiring an upgrade to mitigate.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Yes, since 4 Nov 2025 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Oct 2025
- **Updated:** 21 Sep 2026
- **Also known as:** GHSA-hj6h-fpv2-5h4v

## What is CVE-2025-11371?

CVE-2025-11371 is a high-severity path traversal vulnerability in Gladinet CentreStack and TrioFox, published on 9 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In the default installation and configuration of Gladinet CentreStack and TrioFox, there is an unauthenticated Local File Inclusion Flaw that allows unintended disclosure of system files. Exploitation of this vulnerability has been observed in the wild. 

This issue impacts Gladinet CentreStack and Triofox: All versions prior to and including 16.7.10368.56560

Weakness: CWE-552 (Files or Directories Accessible to External Parties)

## Which versions are affected by CVE-2025-11371?

It affects 2 products.


Products: Gladinet Centrestack, Gladinet Triofox.

## How do I fix CVE-2025-11371?

No fix has been published for CVE-2025-11371 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 25 Nov 2025.

## Is CVE-2025-11371 being exploited?

Yes. Attackers have exploited CVE-2025-11371 in the wild since at least 4 Nov 2025.

Public exploit code:

- Detection for CVE-2025-11371 (github_poc): https://github.com/rxerium/CVE-2025-11371
- CVE-2025-11371 PoC, credit goes to Huntress, https://www.huntress.com/blog/gladinet-centrestack-triofox-local-file-inclusion-flaw (github_poc): https://github.com/lap1nou/CVE-2025-11371
- https://github.com/NetVanguard-cmd/CVE-2025-11371 (github_poc): https://github.com/NetVanguard-cmd/CVE-2025-11371
- Gladinet CentreStack/Triofox Path Traversal (metasploit)
- Gladinet CentreStack & TrioFox - Local File Inclusion (nuclei): http/cves/2025/CVE-2025-11371.yaml

## Other vulnerabilities in Gladinet CentreStack and TrioFox

- [CVE-2025-30406](https://insights.sbomify.com/CVE-2025-30406/): Gladinet CentreStack and Triofox Use of Hard-coded Cryptographic Key (critical 9.0, exploited in the wild)
- [CVE-2025-14611](https://insights.sbomify.com/CVE-2025-14611/): Gladinet CentreStack and Triofox Hard Coded Cryptographic (high 7.1, exploited in the wild)
- [CVE-2023-26829](https://insights.sbomify.com/CVE-2023-26829/): Auth bypass in n/a (critical 9.8)
- [CVE-2023-26830](https://insights.sbomify.com/CVE-2023-26830/): File upload in n/a (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-11371 and fix it if it is affected.

What it is: CVE-2025-11371 is a high-severity path traversal vulnerability in Gladinet CentreStack and TrioFox, published on 9 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2025-11371 in the wild since at least 4 Nov 2025.

Affected product: Gladinet CentreStack and TrioFox. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-11371/ (Markdown: https://insights.sbomify.com/CVE-2025-11371/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-11371
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-11371
- OSV: https://osv.dev/vulnerability/CVE-2025-11371

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-11371/
Summaries are generated and may contain mistakes; the official description above is the record.