CVE-2025-34256
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 · uneditedAdvantech WISE-DeviceOn Server versions prior to 5.4 contain a hard-coded cryptographic key vulnerability. The product uses a static HS512 HMAC secret for signing EIRMMToken JWTs across all installations. The server accepts forged JWTs that need only contain a valid email claim, allowing a remote unauthenticated attacker to generate arbitrary tokens and impersonate any DeviceOn account, including the root super admin. Successful exploitation permits full administrative control of the DeviceOn instance and can be leveraged to execute code on managed agents through DeviceOn’s remote management features.
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 confidenceAdvantech WISE-DeviceOn Server versions before 5.4 use a hard-coded static HS512 HMAC secret for signing EIRMMToken JWTs across all installations. An unauthenticated attacker can forge JWTs containing only a valid email claim to impersonate any user, including the root super admin, gaining full administrative control and remote code execution capability on managed agents.
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< 5.4CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify WISE-DeviceOn Server installationCheck for the WISE-DeviceOn Server installation by looking for the service named 'WISE-DeviceOn' or checking common installation directories such as C:\Program Files\Advantech\WISE-DeviceOn or /opt/wise-deviceon. On Windows, also check Services.msc for the service entry.Affected if The software is installed on the system
-
Determine installed versionCheck the installed version by examining the file version ofWISE-DeviceOn Server.exe in the installation directory, or access the web interface and navigate to System > About to view the version information.Affected if The version shown is before 5.4 (for example, 5.3.x, 5.2.x, etc.)
-
Verify JWT configuration for EIRMMTokenExamine the configuration files in the installation directory for any JWT-related settings. Look for files containing 'EIRMMToken' or 'JWT' in the config folder. Check for a static HMAC secret key in configuration or code.Affected if A hard-coded static secret is found in configuration files rather than a unique per-instance secret
If WISE-DeviceOn Server is installed and the version is before 5.4, the environment is affected by this hard-coded JWT signing secret vulnerability.
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 · scoped5.4
Upgrade to version 5.4 or later which must implement per-instance cryptographic secrets. Immediately rotate any exposed credentials and invalidate all existing sessions/tokens.
Wise DeviceOn Server 5.4
- 1. Back up the current Wise DeviceOn Server configuration and all relevant data
- 2. Obtain Wise DeviceOn Server version 5.4 from the official Advantech download source (advcloudfiles.advantech.com or docs.deviceon.advantech.com)
- 3. Follow Advantech's official upgrade procedure to install version 5.4
- 4. After upgrade, verify the server is running version 5.4
- 5. Test JWT token authentication to confirm the hard-coded key has been replaced
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-34256 — 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-34256 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