# CVE-2025-34264: Advantech WISE-DeviceOn Server < 5.4 Authenticated Stored XSS via dog/{agentId}

> Authenticated attackers can inject scripts via process names in WISE-DeviceOn Server, leading to session compromise for other users.

- **Severity:** Medium 5.1 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Dec 2025
- **Updated:** 14 Aug 2026
- **Also known as:** GHSA-p8wc-v68c-38qm

## What is CVE-2025-34264?

CVE-2025-34264 is a medium-severity cross-site scripting vulnerability in Advantech Co., Ltd. WISE-DeviceOn Server, published on 5 Dec 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Advantech 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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2025-34264?

It affects 1 product.


Products: Advantech Wise-Deviceon Server.

## How do I fix CVE-2025-34264?

No fix has been published for CVE-2025-34264 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-34264 being exploited?

There is no known exploitation of CVE-2025-34264 in the wild and no public exploit code.

## Other vulnerabilities in Advantech Co., Ltd. WISE-DeviceOn Server

- [CVE-2025-34256](https://insights.sbomify.com/CVE-2025-34256/): Advantech WISE-DeviceOn Server < 5.4 Hard-coded JWT Key Authentication Bypass (critical 10.0)
- [CVE-2025-34257](https://insights.sbomify.com/CVE-2025-34257/): Advantech WISE-DeviceOn Server < 5.4 Authenticated Stored XSS via action/defined (medium 5.1)
- [CVE-2025-34258](https://insights.sbomify.com/CVE-2025-34258/): Advantech WISE-DeviceOn Server < 5.4 Authenticated Stored XSS via devicemap/plan (medium 5.1)
- [CVE-2025-34259](https://insights.sbomify.com/CVE-2025-34259/): Advantech WISE-DeviceOn Server < 5.4 Authenticated Stored XSS via devicemap/building (medium 5.1)
- [CVE-2025-34260](https://insights.sbomify.com/CVE-2025-34260/): Advantech WISE-DeviceOn Server < 5.4 Authenticated Stored XSS via action/schedule (medium 5.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-34264 and fix it if it is affected.

What it is: CVE-2025-34264 is a medium-severity cross-site scripting vulnerability in Advantech Co., Ltd. WISE-DeviceOn Server, published on 5 Dec 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-34264 in the wild and no public exploit code.

Affected product: Advantech Co., Ltd. WISE-DeviceOn Server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-34264/ (Markdown: https://insights.sbomify.com/CVE-2025-34264/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-34264
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-34264
- OSV: https://osv.dev/vulnerability/CVE-2025-34264

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-34264/
Summaries are generated and may contain mistakes; the official description above is the record.