basicsecurity.net
Proof, not just disclosure.
Threats / Gladinet / CVE-2025-30406
CVE-2025-30406 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Gladinet CentreStack vulnerability

Gladinet CentreStack uses hard-coded cryptographic keys for ViewState integrity verification, allowing attackers to forge payloads and achieve remote code execution.

Verdict

Today item — known-exploited.

An attacker can exploit hard-coded cryptographic keys to forge ViewState payloads, bypass integrity checks, and execute arbitrary code on affected CentreStack instances. This vulnerability is actively exploited in the wild.

CISA KEV Yes · 2025-04-083EPSS 0.92287 (verify live)4Exploit Weaponized · public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
159 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-04-08).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.92287 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Gladinet, CentreStack. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-321 CWE-321 — weakness family: Cryptography.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-321 · CWE-321Cryptography
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution 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 board
1

Front door — unauthenticated access narrative 1

Attacker
I obtain the hard-coded cryptographic key from the CentreStack application binary or source.
Business
The organization loses exclusive control over ViewState integrity verification, enabling unauthorized code execution.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I craft a malicious ViewState payload signed with the hard-coded key and submit it to the application.
Business
The application deserializes the forged payload, treating it as legitimate and executing embedded malicious code.
3

Lateral reach — past segmentation narrative 3

Attacker
I achieve remote code execution with the privileges of the CentreStack application process.
Business
The organization experiences unauthorized system compromise, data theft, and potential lateral movement within the infrastructure.
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’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • Weaponized exploit available (VulnCheck)
  • 159 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Public exploit availability
  • Catalogued by mitre (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by mitreCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.