Security readout for executives and security teams
Plain-English summary
An authenticated user can save a malicious device name in WISE-DeviceOn Server before version 5.4. When another user views that device, the browser may execute the stored script with the victim’s application privileges, risking session compromise and unauthorized actions. Authentication and victim interaction limit severity, but administrator exposure could increase business impact.
Executive priority
Schedule prompt remediation through the normal vulnerability process, prioritizing externally reachable or multi-user management servers. Escalate urgency where low-trust users can rename devices or administrators may have viewed suspicious records. This is not supported as an emergency active-exploitation event by the supplied evidence.
Technical view
The /rmm/v1/devices/name/{agent_id} endpoint stores new_name without adequate HTML sanitization. Device listing or detail views later render the value, producing persistent cross-site scripting. The CVSS 4.0 score is 5.1: network-accessible, low complexity, low privileges required, passive user interaction, and limited confidentiality and integrity impacts across contexts.
Likely exposure
Deployments running WISE-DeviceOn Server earlier than 5.4 are potentially exposed where users can rename devices. Internet accessibility increases reach but is not required; an attacker must first possess authenticated access. Risk is greater when privileged operators view attacker-controlled device records.
Exploitation context
The supplied record is not in KEV and provides no evidence of active exploitation. Exploitation requires an authenticated user to store a crafted device name and another user to view or interact with it. No exploit maturity or observed campaign information is established by the supplied sources.
Researcher notes
CWE-79 applies. The narrative identifies versions before 5.4, but the structured affected entry contains the ambiguous value “0” with default status unaffected. Confirm precise version applicability against Advantech’s advisory. Assess stored output encoding, rename authorization, session protections, affected views, and audit evidence without assuming exploitation.
Mitigation direction
- Upgrade WISE-DeviceOn Server to version 5.4 or later following Advantech guidance.
- Restrict device-renaming privileges to trusted users until the upgrade is complete.
- Limit administrative interface access using network controls and strong authentication.
- Review stored device names for unexpected markup or script-like content.
- Invalidate potentially exposed sessions if suspicious device names were viewed.
Validation and detection
- Inventory WISE-DeviceOn Server instances and record their exact versions.
- Confirm every deployment is version 5.4 or later.
- Review authorization rules for the device-renaming endpoint.
- Verify device names are safely encoded in listing and detail views.
- Inspect audit logs for suspicious renames and subsequent privileged views.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2025-34262 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.1 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
5.1MediumVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://advcloudfiles.advantech.com/cms/2ca1b071-fd78-4d7f-8a2a-7b4537a95d19/Security%20Advisory%20PDF%20File/SECURITY-ADVISORY----DeviceOn-20251208-2.pdfCVE reference, VulnCheck · vendor-advisory, patch
- https://docs.deviceon.advantech.com/docs/resource/CVE reference, VulnCheck · product
- https://www.vulncheck.com/advisories/advantech-wise-deviceon-server-authenticated-stored-xss-via-devices-name-agentidCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.