dbcve.org
Wise Deviceon ServerApplication · Advantech

CVE-2025-34261

MEDIUM · 5.4 CVSS v3.1 Published 2025-12-05
Fix available
A fix is available. Upgrade to 5.4 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Advantech WISE-DeviceOn Server versions prior to 5.4 contain a stored cross-site scripting (XSS) vulnerability in the /rmm/v1/devicegroups/ endpoint. When an authenticated user creates a device group, the name and description values are stored and later rendered in device group listings without proper HTML sanitation. An attacker can inject malicious script into either field, which is then executed in the browser context of users who view or interact with the affected device group, potentially enabling session compromise and unauthorized actions as the victim.

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

Advantech WISE-DeviceOn Server versions prior to 5.4 contain a stored XSS vulnerability in the /rmm/v1/devicegroups/ endpoint. Authenticated users can inject malicious JavaScript into device group name or description fields. This unsanitized input is later rendered in device group listings without HTML encoding, causing the script to execute in the browser context of other users viewing those groups.

MitigationUpgrade to version 5.4 or later. Until then, implement output encoding/HTML sanitization on all user-supplied input before rendering in the device group listings.

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
Wise Deviceon ServerApplication
Affected:< 5.4

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

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. Identify WISE-DeviceOn Server version
    Locate the installation directory or check the applicationAbout page in the WISE-DeviceOn web interface to find the installed version number
    Affected if The installed version is lower than 5.4 (e.g., 5.3.x, 5.2.x, etc.)
  2. Confirm API endpoint accessibility
    Verify that the /rmm/v1/devicegroups REST API endpoint is accessible by attempting to access it with valid authentication credentials
    Affected if The endpoint returns a successful response and accepts requests
  3. Review device group configurations
    Query or inspect existing device groups through the /rmm/v1/devicegroups endpoint or the web UI to examine the group names and descriptions stored in the system
    Affected if Device groups exist with names or descriptions containing user-supplied input that may not be properly encoded
  4. Check rendering of device group listings
    Access the device group listing page in the web interface and inspect the page source or use browser developer tools to see if HTML special characters in group names or descriptions are encoded or rendered as plain text
    Affected if HTML characters like <, >, or & appear unencoded when viewing device group listings, indicating no output encoding is applied

You are affected if running WISE-DeviceOn Server version below 5.4 AND the device group listing page renders user-supplied group names or descriptions without HTML encoding, allowing script execution in browsers.

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 5.4 or later
Fixed in 5.4
Interim mitigation

Upgrade to version 5.4 or later. Until then, implement output encoding/HTML sanitization on all user-supplied input before rendering in the device group listings.

Recommended fix High confidence

WISE-DeviceOn Server 5.4

  1. Obtain WISE-DeviceOn Server version 5.4 from official Advantech channels (advcloudfiles.adventech.com or through your Advantech support contact)
  2. Follow the standard WISE-DeviceOn Server upgrade procedure to install version 5.4
  3. Verify the upgrade completed successfully
  4. Confirm the /rmm/v1/devicegroups/ endpoint now properly sanitizes HTML in device group name and description fields

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

Fix this in Wise Deviceon Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-34261 — 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-34261 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