CVE-2025-11371
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 · uneditedIn 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
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 confidenceThis is an unauthenticated Local File Inclusion (LFI) vulnerability in the default installation of Gladinet CentreStack and TrioFox file sync and share solutions. Attackers can exploit this flaw to read arbitrary system files on the server without any authentication credentials. The vulnerability has been observed being exploited in the wild, indicating active targeting of vulnerable installations.
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.10.10408.56683<= 16.7.10368.56560CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 versionAccess the CentreStack administration console or check the software's built-in 'About' or 'Version' page typically found under Help or Settings. Alternatively, inspect the application binaries or installer for version metadata.Affected if The displayed version is lower than 16.10.10408.56683 (for CentreStack).
-
Identify installed TrioFox versionAccess the TrioFox administration panel or check the application's version information typically accessible through the Help or System Information section.Affected if The displayed version is 16.7.10368.56560 or lower (for TrioFox).
-
Verify default installation exposureConfirm that the CentreStack or TrioFox web interface is accessible from untrusted networks without authentication barriers such as VPN, IP whitelisting, or two-factor authentication in place.Affected if The application is exposed to the public internet or untrusted internal networks without additional access controls, as the vulnerability is unauthenticated.
-
Review web server logs for traversal patternsExamine IIS, Apache, or nginx logs (depending on hosting platform) for unusual request patterns containing directory traversal sequences such as '../' or file path attempts to system files like '/etc/passwd' or 'C:\Windows\'.Affected if Logs contain requests with traversal patterns targeting system directories or known sensitive files, indicating potential exploitation attempts.
You are affected if CentreStack version is below 16.10.10408.56683 or TrioFox version is 16.7.10368.56560 or lower, AND the application is network-accessible without authentication barriers.
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.10.10408.56683
Apply the vendor-supplied patch when available; until then, restrict network access to CentreStack/TrioFox services and monitor for indicators of compromise. Consider deploying a WAF rule to block path traversal patterns in requests.
CentreStack: upgrade to 16.10.10408.56683 or later | Triofox: upgrade to 16.10.x or later
- Identify the currently installed CentreStack or Triofox version by checking the About section in the admin dashboard
- Download the latest patched version from the official Gladinet download portal or your licensed customer portal
- Schedule a maintenance window and create a complete backup of the current installation, including the database and configuration files
- Stop the CentreStack/Triofox services before applying the upgrade
- Run the installer for version 16.10.10408.56683 or later for CentreStack, or version 16.10.x or later for Triofox
- Follow the on-screen upgrade wizard, preserving existing configuration settings
- Start the services and verify the application is operational
- Review system logs for any errors or anomalies following the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11371 — 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-11371 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