Home › Intelligence › Brief
VULNERABILITY BRIEF🟠 High Vulnerability

Hard‑coded Cryptographic Key in Gladinet CentreStack & Triofox Enables Remote Code Execution (CVE‑2025‑30406)

Gladinet CentreStack and Triofox embed a static cryptographic key used for ViewState integrity, allowing attackers to forge payloads and achieve remote code execution. The flaw highlights the need for robust key‑management controls and audit‑ready evidence of remediation.

LiveThreat™ Intelligence · 📅 October 07, 2026· 📰 nvd.nist.gov
🟠
Severity
High
VU
Type
Vulnerability
🎯
Confidence
High
🏢
Affected
1 sector(s)
✅
Actions
2 recommended
📰
Source
nvd.nist.gov

CVE‑2025‑30406: Hard‑coded Cryptographic Key in Gladinet CentreStack & Triofox Enables Remote Code Execution

What It Is – Gladinet CentreStack and its Triofox front‑end embed a hard‑coded cryptographic key that is used to protect ViewState integrity. The static key lets an attacker craft malicious ViewState payloads that survive integrity checks and are deserialized on the server, leading to remote code execution.

Exploitability – The vulnerability is publicly disclosed in the CISA Known Exploited Vulnerabilities (KEV) catalog, indicating that exploit code is known to be in the wild. CVSS v3.1 scores it at 9.8 (High).

Affected Products – Gladinet CentreStack (on‑premises and cloud‑hosted deployments) and the Triofox web interface that ships with the same code base.

Why It Matters for Trust & Control Assurance

  • Cryptographic key management – Hard‑coded secrets violate the control objective of protecting cryptographic keys and application secrets, a requirement across SOC 2, ISO 27001, NIST CSF and many other frameworks.
  • Continuous control monitoring – Detecting static keys requires evidence‑driven monitoring of code repositories and runtime configurations; without it, organizations cannot demonstrate due‑diligence during audits.
  • Defensible audit trail – Remediating the flaw and documenting key rotation provides the audit‑ready artifacts buyers now demand when evaluating SaaS providers.

Recommended Actions

  • Inventory all Gladinet CentreStack/Triofox instances and verify the version.
  • Apply vendor patch as soon as it is released; if unavailable, implement a temporary mitigation by disabling ViewState or enforcing server‑side encryption with a managed key.
  • Rotate any static keys used for ViewState integrity and replace them with keys stored in a centralized, hardware‑backed key management service (KMS).
  • Update control evidence – capture screenshots of key‑management policies, KMS integration logs, and patch‑deployment records for audit purposes.
  • Integrate into continuous monitoring – add a rule to your configuration‑as‑code scans that flags hard‑coded secrets in deployed artifacts.

Source: CISA KEV – CVE‑2025‑30406

📰 Original Source
https://nvd.nist.gov/vuln/detail/CVE-2025-30406 ↗

This LiveThreat Intelligence Brief is an independent analysis. Read the original reporting at the link above.

From the Verisq platform · Trust Operations

Answer one control objective. Answer ten frameworks.

The Verisq Common Framework is a spine of 84 control objectives that SOC 2, ISO 27001, NIST CSF, CMMC, HIPAA, PCI DSS, HITRUST, GDPR, ISO 42001 and NIST AI RMF map onto — each graded honestly. Satisfy an objective once and every framework that recognizes it lights up at its real strength.

See how the Verisq Common Framework works →