Threats / Gladinet / CVE-2025-14611
CVE-2025-14611
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-09-19
Gladinet CentreStack and Triofox vulnerability
Gladinet CentreStack and Triofox contain hardcoded cryptographic keys in their AES implementation, enabling unauthenticated attackers to bypass encryption on public endpoints and achieve arbitrary local file inclusion.
Verdict
Today item — known-exploited.
Hardcoded cryptographic material (CWE-798) in widely deployed file-sync products creates a direct path to unauthenticated remote file access. Active exploitation in the wild indicates immediate operational risk for exposed instances.
CISA KEV Yes · 2025-12-155EPSS 0.53302 (verify live)6Exploit Public PoC7CVSS 7.13CISA SSVC Exploitation: active · Automatable: no · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
7 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-12-15).
Probability (EPSS)
EPSS 0.53302 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 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) · Affected: Gladinet, CentreStack and Triofox. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 4.0, set at disclosure.
Weakness (CWE)
Mapped to CWE-798 Hard-coded Credentials — weakness family: Authentication.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 3 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a public proof-of-concept / detection template). Catalog entries: Metasploit module, nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I extract the hardcoded AES key from the application or public documentation to decrypt traffic to exposed endpoints.
Business
Encryption controls fail to protect data in transit, violating confidentiality assumptions for file-sync infrastructure.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I craft a specially formed request using the known key to bypass authentication checks on file-access endpoints.
Business
Access controls are circumvented, allowing unauthorized file retrieval without valid credentials or audit trail.
3
Lateral reach — past segmentation narrative 3
Attacker
I exploit local file inclusion to read arbitrary files from the server filesystem, including configuration and sensitive data.
Business
Confidential files, credentials, and system configuration are exposed, enabling lateral movement and data exfiltration.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Found an error? Propose a correction.
A correction is a cited counter-claim — it must cite a source,
gets reviewed by a second human, and is never auto-applied. See the
correction convention and our identity
npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y.