dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 29 Apr 2025.
CentrestackApplication · Gladinet

CVE-2025-30406

CRITICAL · 9.8 CVSS v3.1 Published 2025-04-03
Fix available
A fix is available. Upgrade to 16.4.10315.56368 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Remotely reachable No privileges Zero-click Patch available

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 · unedited
Gladinet CentreStack through 16.1.10296.56315 (fixed in 16.4.10315.56368) has a deserialization vulnerability due to the CentreStack portal's hardcoded machineKey use, as exploited in the wild in March 2025. This enables threat actors (who know the machineKey) to serialize a payload for server-side deserialization to achieve remote code execution. NOTE: a CentreStack admin can manually delete the machineKey defined in portal\web.config.

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 confidence

Gladinet CentreStack through version 16.1.10296.56315 contains a deserialization vulnerability caused by a hardcoded machineKey in portal/web.config. Attackers who obtain this static machineKey can craft malicious serialized payloads that, when deserialized by the CentreStack portal server, result in remote code execution. This vulnerability has been actively exploited in the wild.

MitigationUpgrade to CentreStack version 16.4.10315.56368 or later; alternatively, manually delete the hardcoded machineKey from portal\web.config as an immediate workaround.

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
CentrestackApplication
Affected:< 16.4.10315.56368

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate CentreStack installation directory
    Search for the CentreStack installation path, typically found in C:\Program Files\Gladinet CentreStack\ or C:\Inetpub\wwwroot\, or check for the portal\web.config file mentioned in the CVE.
    Affected if CentreStack is installed on the system.
  2. Check installed CentreStack version
    Open the CentreStack administration console and navigate to the About or System Information page to view the exact version number, or check the file version of the main executable.
    Affected if The installed version is lower than 16.4.10315.56368.
  3. Locate and inspect portal\web.config
    Navigate to the portal subdirectory within the CentreStack installation and open web.config in a text editor to examine its contents.
    Affected if The web.config file exists and is readable.
  4. Identify hardcoded machineKey element
    Search within the web.config file for the <machineKey> element. Examine the validationKey and decryptionKey attributes to determine if they contain static hardcoded values rather than being generated or empty.
    Affected if A <machineKey> element exists with non-empty validationKey and/or decryptionKey attributes containing static values.

You are affected if CentreStack is installed with a version below 16.4.10315.56368 AND the portal\web.config file contains a hardcoded machineKey with static validationKey/decryptionKey values.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 16.4.10315.56368 or later
Fixed in 16.4.10315.56368
Vendor patch gladinetsupport.s3.us-east-1.amazonaws.com →
Interim mitigation

Upgrade to CentreStack version 16.4.10315.56368 or later; alternatively, manually delete the hardcoded machineKey from portal\web.config as an immediate workaround.

Recommended fix High confidence

16.4.10315.56368 or later

  1. Obtain CentreStack version 16.4.10315.56368 or later from the official vendor (www.centrestack.com)
  2. Back up the current CentreStack configuration and all data
  3. Upgrade CentreStack to version 16.4.10315.56368 or later following the vendor's standard upgrade procedures
  4. After upgrade, verify the portal is accessible and the service is running properly
  5. Alternatively, as a configuration workaround, manually delete the machineKey defined in portal\web.config (note: this may affect session management and should be tested)

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Centrestack Exploited in the wild — priority engagement
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-30406 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-30406 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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