dbcve.org
Wise Deviceon ServerApplication · Advantech

CVE-2025-34263

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/plugin-config/dashboards/menus endpoint. When an authenticated user adds or edits a dashboard entry, the label and path values are stored in plugin configuration data and later rendered in the dashboard UI 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 dashboard, 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/plugin-config/dashboards/menus endpoint where dashboard label and path values are stored and later rendered in the UI without proper HTML sanitization, allowing injection of malicious scripts that execute in victim browsers.

MitigationImplement input validation and output encoding/sanitization for dashboard label and path fields before storage and before rendering in the UI to prevent script injection.

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 installed WISE-DeviceOn Server version
    Locate the WISE-DeviceOn Server installation and check its version number. This is typically found in the application itself, an about page, or installation metadata.
    Affected if The installed version is prior to 5.4 (e.g., 5.3.x, 5.2.x, earlier). Versions 5.4 and later are not affected.
  2. Confirm the /rmm API endpoint exists and is accessible
    Verify that the endpoint /rmm/v1/plugin-config/dashboards/menus is accessible on the server. This may require authentication depending on the deployment configuration.
    Affected if The endpoint responds and allows access to dashboard configuration functions.
  3. Check for existing dashboard configurations
    Inspect the dashboard configuration data stored on the server or in the database. Look for entries under the dashboards/menus path that contain label and path field values.
    Affected if There are stored dashboard configurations with label and path fields present in the system.
  4. Inspect rendered dashboard UI elements
    Access the WISE-DeviceOn Server web interface and navigate to the dashboards section. View the rendered HTML of dashboard labels and paths to check if HTML special characters are encoded or raw.
    Affected if Dashboard labels or paths render unencoded HTML characters (e.g., <script> tags visible in source or executed) indicating lack of output sanitization.

The environment is affected if WISE-DeviceOn Server version is prior to 5.4 AND the /rmm/dashboards/menus functionality is accessible AND dashboard configurations are stored and rendered in the UI without sanitization.

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

Implement input validation and output encoding/sanitization for dashboard label and path fields before storage and before rendering in the UI to prevent script injection.

Recommended fix High confidence

5.4

  1. Upgrade Advantech WISE-DeviceOn Server to version 5.4 or later
  2. After upgrading, verify the /rmm/v1/plugin-config/dashboards/menus endpoint now properly sanitizes label and path values before rendering
  3. Confirm that existing dashboard configurations with previously injected scripts no longer execute in the browser context

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

Fix this in Wise Deviceon Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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