CVE-2025-14611
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedGladinet 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceGladinet CentreStack and Triofox prior to version 16.12.10420.56791 use hardcoded values in their AES encryption implementation, creating weak crypto that exposes publicly accessible endpoints. Combined with the absence of authentication, this enables unauthenticated arbitrary local file inclusion attacks that can lead to full system compromise when chained with other vulnerabilities.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 16.12.10420.56791< 16.12.10420.56791CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed CentreStack or Triofox versionAccess the web administration interface and navigate to the About or System Information page, or check the installation directory for a version file. On Windows, check the program files folder or the installation log files for version information.Affected if The displayed version number is lower than 16.12.10420.56791 for either CentreStack or Triofox.
-
Confirm product typeVerify whether the affected instance is CentreStack or Triofox, as both products share the same vulnerability. Check the product name displayed in the web interface login page or title.Affected if The product is Gladinet CentreStack or Gladinet Triofox.
-
Determine if web interface is publicly exposedPerform an external network scan or access the web interface URL from an untrusted network (or use a third-party service like.shodan.io) to confirm whether port 443 or 80 is accessible from the internet. Alternatively, review firewall rules and network configuration to identify exposure.Affected if The CentreStack or Triofox web interface is reachable from public IP addresses without VPN or network segmentation.
-
Inspect configuration files for hardcoded cryptographic valuesLocate and examine configuration files in the application installation directory, particularly those related to encryption settings or key management. Look for hardcoded AES keys, initialization vectors, or similar cryptographic constants in XML or config files.Affected if Hardcoded AES keys or cryptographic values are present in configuration files rather than being retrieved from a secure key management system.
-
Check for local file inclusion indicatorsReview web application logs for suspicious requests containing paths like ../, ..\, or /etc/passwd. Test a known endpoint with a benign LFI payload (e.g., adding ?file=../web.config) and observe the response for file contents.Affected if The application returns file contents in response to LFI-style path traversal requests, indicating the LFI vulnerability is present.
The environment is affected if CentreStack or Triofox version is below 16.12.10420.56791 AND the web interface is accessible from public networks, allowing unauthenticated attackers to exploit hardcoded AES keys for local file inclusion.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped16.12.10420.56791
Upgrade CentreStack and Triofox to version 16.12.10420.56791 or later to replace hardcoded AES values with proper key management. If immediate patching is not possible, restrict network access to the affected endpoints.
16.12.10420.56791
- 1. Identify the currently installed version of CentreStack or Triofox by accessing the admin console or checking the application version information
- 2. If the installed version is below 16.12.10420.56791, plan for an upgrade during a maintenance window
- 3. Perform a complete backup of the CentreStack/Triofox deployment including configuration files and database
- 4. Download the fixed version 16.12.10420.56791 from the official Gladinet vendor channels or your licensed distribution source
- 5. Follow Gladinet's official upgrade documentation to apply the update, ensuring all pre-upgrade prerequisites are met
- 6. After upgrade completion, verify the new version displays as 16.12.10420.56791 or later in the admin interface
- 7. Test critical functionality including authentication, file access, and any custom integrations to confirm proper operation
- 8. Review CISA and Huntress advisories for any additional post-upgrade hardening recommendations
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14611 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-14611 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data