# CVE-2025-14611: Gladinet CentreStack and Triofox Hard Coded Cryptographic

> Hardcoded AES keys in Gladinet CentreStack allow unauthenticated attackers to achieve arbitrary local file inclusion and potential full system compromise.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:H/SI:H/SA:H/E:A`)
- **Exploited in the wild:** Yes, since 15 Dec 2025 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Dec 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-j7r7-3wrm-f59w

## What is CVE-2025-14611?

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

### Official description

Gladinet CentreStack and Triofox prior to version 16.12.10420.56791 used hardcoded values for their implementation of the AES cryptoscheme. This degrades security for public exposed endpoints that may make use of it and may offer arbitrary local file inclusion when provided a specially crafted request without authentication. This opens the door for future exploitation and can be leveraged with previous vulnerabilities to gain a full system compromise.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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

It affects 2 products.


Products: Gladinet Centrestack, Gladinet Triofox.

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

No fix has been published for CVE-2025-14611 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 5 Jan 2026.

## Is CVE-2025-14611 being exploited?

Yes. Attackers have exploited CVE-2025-14611 in the wild since at least 15 Dec 2025.

Public exploit code:

- Gladinet CentreStack/Triofox Access Ticket Forge (metasploit)
- CVE-2025-14611 CentreStack and Triofox full Poc/Exploit (github_poc): https://github.com/pl4tyz/CVE-2025-14611-CentreStack-and-Triofox-full-Poc-Exploit
- Gladinet CentreStack & Triofox - Hardcoded Credentials (nuclei): http/cves/2025/CVE-2025-14611.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-11371](https://insights.sbomify.com/CVE-2025-11371/): Gladinet CentreStack and Triofox Files or Directories Accessible to External Parties (high 7.5, 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-14611 and fix it if it is affected.

What it is: CVE-2025-14611 is a high-severity vulnerability in Gladinet CentreStack and TrioFox, published on 12 Dec 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-14611 in the wild since at least 15 Dec 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-14611/ (Markdown: https://insights.sbomify.com/CVE-2025-14611/index.md)
```

## Sources

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

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