CVE-2025-34264
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/dog/{agentId} endpoint. When an authenticated user adds or edits Software Watchdog process rules for an agent, the monitored process name is stored in the settings array and later rendered in the Software Watchdog UI without proper HTML sanitation. An attacker can inject malicious script into the process name, which is then executed in the browser context of users who view or interact with the affected rules, 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 have a stored XSS vulnerability in the Software Watchdog feature. The /rmm/v1/dog/{agentId} endpoint accepts process names when creating or editing monitoring rules but stores them without sanitization. When other users view these rules in the UI, the process name is rendered without proper HTML encoding, allowing injected JavaScript to execute in their browser sessions.
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 versionLocate the installed version of WISE-DeviceOn Server through the application UI (typically in About or System Info section) or by checking the installation directory for version metadataAffected if The installed version is prior to 5.4 (any version number less than 5.4)
-
Verify Software Watchdog feature accessLog into the WISE-DeviceOn Server interface and navigate to the Software Watchdog feature (typically under Device Management or Monitoring sections)Affected if The Software Watchdog feature is accessible and enabled in the current environment
-
Inspect existing watchdog rules for unsanitized inputAccess the watchdog rule configuration and review any existing process monitoring rules. Check the process name fields for any suspicious characters or patterns that could indicate XSS payloads (such as <script>, javascript:, onerror, etc.)Affected if There are watchdog rules containing process names with HTML or script tags, or any unsanitized special characters
-
Review recent rule creation or modification activityCheck the audit logs or activity logs for the /rmm/v1/dog/ endpoint to identify any recent create or update operations on watchdog rules, especially those with unusual process name valuesAffected if There are recent rule modifications with potentially malicious process names that were not properly sanitized
A user is affected if they are running WISE-DeviceOn Server version prior to 5.4 AND have the Software Watchdog feature accessible, with any existing rules containing unsanitized process names that could execute JavaScript
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 which includes proper input validation and output encoding. Until then, restrict administrative access to the Software Watchdog feature and monitor for suspicious process names.
WISE-DeviceOn Server 5.4
- Back up the current WISE-DeviceOn Server configuration and any critical data
- Download the WISE-DeviceOn Server version 5.4 from the official Advantech source (advcloudfiles.advantech.com or docs.deviceon.advantech.com)
- Stop the WISE-DeviceOn Server service
- Install version 5.4 following the standard upgrade procedure
- Start the WISE-DeviceOn Server service
- Verify the upgrade was successful by logging into the admin interface
- Confirm the XSS vulnerability is resolved by testing that process names are properly sanitized in the Software Watchdog UI
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-34264 — 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-34264 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