CVE-2025-34262
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 stored cross-site scripting (XSS) vulnerability in the /rmm/v1/devices/name/{agent_id} endpoint. When an authenticated user renames a device, the new_name value is stored and later rendered in device listings or detail views without proper HTML sanitation. An attacker can inject malicious script into the device name, which is then executed in the browser context of users who view or interact with the affected device, 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 confidenceAdvantech WISE-DeviceOn Server versions prior to 5.4 contain a stored XSS vulnerability in the /rmm/v1/devices/name/{agent_id} API endpoint. Authenticated users can inject malicious JavaScript into the device new_name parameter during rename operations. This payload is stored and rendered without proper HTML sanitization in device listings and detail views, executing in the browser context of users who view or interact with the affected device.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify WISE-DeviceOn Server installationLocate the WISE-DeviceOn Server application and determine its installation path. Check for running services or processes named 'WISE-DeviceOn', 'DeviceOn', or 'WISE-PaaS/DeviceOn' in your environment.Affected if The server is running Advantech WISE-DeviceOn Server software.
-
Determine installed versionCheck the installed version of WISE-DeviceOn Server. Common locations include: the application's About/Version page in the web UI, installation directory files (such as version.txt, manifest, or config files), or the docker image tag if running in containers.Affected if The installed version is any version prior to 5.4 (for example: 5.3.x, 5.2.x, 5.1.x, 5.0.x, or earlier releases).
-
Verify API endpoint accessibilityConfirm the REST API is accessible at the /rmm/v1/devices/ endpoint. This is typically found at https://[your-server]/rmm/v1/. Check if authentication is configured and functional.Affected if The /rmm/v1/devices/name/{agent_id} API endpoint is reachable and accepts requests.
-
Check device rename functionalityInspect the application's device management features to determine if device renaming is enabled. Look for device name edit options in the web UI or verify the new_name parameter is accepted by the API.Affected if Device rename operations via the new_name parameter are permitted in the environment.
-
Inspect stored device names for unsanitized contentReview existing device names in the database or device listing views. Examine the HTML rendering of device names in both list views and detail views to identify any unsanitized characters or script tags.Affected if Device names contain raw HTML or JavaScript that executes when viewed in the browser, indicating stored XSS is present.
Your environment is affected if WISE-DeviceOn Server version is below 5.4 and the device rename feature using the /rmm/v1/devices/name/{agent_id} API endpoint with the new_name parameter is accessible and functional.
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 WISE-DeviceOn Server version 5.4 or later. Additionally, implement output encoding and input validation for all device name fields across listing and detail view components to prevent XSS execution.
5.4
- 1. Backup the current Wise DeviceOn Server configuration and database.
- 2. Obtain the Wise DeviceOn Server version 5.4 from the official Advantech download portal (advcloudfiles.adventech.com or docs.deviceon.adventech.com).
- 3. Stop the Wise DeviceOn Server service.
- 4. Install version 5.4 following the standard upgrade procedure in the official documentation.
- 5. Verify the upgrade was successful by checking the server version in the admin console.
- 6. Confirm the /rmm/v1/devices/name/{agent_id} endpoint now properly sanitizes the new_name parameter before storage and rendering.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-34262 — 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-34262 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