CVE-2025-34258
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/devicemap/plan endpoint. When an authenticated user adds an area to a map entry, the name parameter is stored and later rendered in the map list without HTML sanitization. An attacker can inject malicious script into the area name, which is then executed in the browser context of users who view or interact with the affected map entry, 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 cross-site scripting (XSS) vulnerability in the /rmm/v1/devicemap/plan endpoint. The area name parameter is not sanitized when stored, and the unsanitized value is rendered in the map list, allowing injected JavaScript to execute in the browser context of users viewing the affected map entry.
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 the installed WISE-DeviceOn Server versionLocate the version number in the application UI (typically in the About or System Info section), in installation logs, or in the server configuration files. Compare this to version 5.4.Affected if The installed version is any release prior to 5.4 (for example, 5.3.x, 5.2.x, or earlier).
-
Verify the RMM module is enabledConfirm that the DeviceOn RMM (Remote Management and Monitoring) module is active on the server. This is typically accessible via the /rmm/ path in the web interface or API.Affected if The RMM module is enabled and accessible, making the vulnerable endpoint available for interaction.
-
Confirm access to the device map plan functionalityCheck if the /rmm/v1/devicemap/plan API endpoint is reachable. This can be verified through API documentation, network traffic analysis, or by accessing the device map configuration in the web UI.Affected if The device map plan feature is accessible and the area name parameter can be submitted through the API or UI.
-
Inspect the area name parameter handlingSubmit a test area name containing HTML or JavaScript characters (such as <script>alert(1)</script>) through the device map plan endpoint. Observe whether the submitted value is stored and rendered back without encoding or sanitization when viewing the map list.Affected if The submitted area name is displayed in the map list without proper HTML encoding, allowing script execution in the browser.
You are affected if your WISE-DeviceOn Server version is below 5.4 and the RMM module with device map functionality is enabled, as the area name parameter is not sanitized before storage or rendering.
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 should include proper HTML sanitization of the area name parameter before storage and before rendering in the map list.
Wise DeviceOn Server version 5.4
- 1. Create a complete backup of the current Wise DeviceOn Server configuration and database
- 2. Download Wise DeviceOn Server version 5.4 from the official Advantech support渠道 (advcloudfiles.advantech.com or through official support)
- 3. Review the official upgrade documentation for Wise DeviceOn Server before proceeding
- 4. Stop the Wise DeviceOn Server service
- 5. Install version 5.4 following the documented upgrade procedure
- 6. Start the Wise DeviceOn Server service
- 7. Verify the server is running correctly and all services are operational
- 8. Log in as an authenticated user and navigate to the device map functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-34258 — 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-34258 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