CVE-2025-34260
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/action/schedule endpoint. When an authenticated user adds a schedule to an existing task, the schedule name is stored and later rendered in schedule listings without HTML sanitation. An attacker can inject malicious script into the schedule name, which is then executed in the browser context of users who view or interact with the affected schedule, 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 · moderate confidenceAdvantech WISE-DeviceOn Server versions before 5.4 contain a stored cross-site scripting vulnerability in the /rmm/v1/action/schedule API endpoint. The schedule name parameter is stored without input validation and subsequently rendered in schedule listings without HTML sanitization, allowing malicious script injection that executes in victim browsers.
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 if Advantech WISE-DeviceOn Server is installedCheck for the WISE-DeviceOn Server application in your environment, typically found running on ports 8080 or 443, or look for the service process on the host.Affected if WISE-DeviceOn Server is present in your environment and the version is unknown or below 5.4
-
Determine the installed version of WISE-DeviceOn ServerAccess the server management interface or check the application binaries for the version number. The version is typically displayed in the UI footer or in the server startup logs.Affected if The installed version is below 5.4 (for example, 5.3.x, 5.2.x, etc.)
-
Verify the /rmm/v1/action/schedule API endpoint is accessibleAttempt to access the /rmm/v1/action/schedule endpoint via the server URL to confirm the API module is enabled and responding.Affected if The endpoint returns HTTP 200 and accepts schedule creation requests, indicating the vulnerable API is active
-
Inspect existing schedule entries for malicious scriptsUse the server UI or API to list all scheduled tasks and examine the schedule name fields for script tags or suspicious HTML patterns like <script>, <img onerror=, or javascript: URLs.Affected if Any schedule entry contains unsanitized HTML or script content in the name field that could execute in a browser
You are affected if WISE-DeviceOn Server version below 5.4 is running and the schedule management feature is accessible, as the stored XSS vulnerability in the /rmm/v1/action/schedule endpoint allows malicious script injection.
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 HTML encoding/sanitization on the schedule name field before rendering and add server-side input validation to reject malicious payloads.
WISE-DeviceOn Server version 5.4
- Upgrade WISE-DeviceOn Server to version 5.4 or later to resolve the stored XSS vulnerability
- After upgrading, verify that the /rmm/v1/action/schedule endpoint now properly sanitizes schedule name input before storage
- Confirm that schedule listings now render schedule names with appropriate HTML encoding to prevent script execution
- Review user permissions to ensure only trusted authenticated users have access to create or modify schedules, following the principle of least privilege
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-34260 — 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-34260 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