CVE-2025-34257
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/defined endpoint. When an authenticated user creates a task, the defined_name value is stored and later rendered in the Overview page without HTML sanitization. An attacker can inject malicious script into defined_name, which is then executed in the browser context of users who view the affected task, 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/action/defined endpoint where the defined_name parameter accepts malicious HTML/JavaScript that is stored in the database and rendered without sanitization on the Overview page, allowing execution in the browser context of users who view the affected task.
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.
-
Check the installed WISE-DeviceOn Server versionLocate the version information for WISE-DeviceOn Server (typically found in the application interface, configuration files, or about page) and compare it to version 5.4Affected if The installed version is prior to 5.4 (e.g., 5.3.x, 5.2.x, etc.)
-
Verify access to the /rmm/v1/action/defined endpointConfirm that the /rmm/v1/action/defined API endpoint is accessible in the WISE-DeviceOn environment (typically via HTTP request to the server's API)Affected if The endpoint is reachable and accepts parameters without authentication restrictions
-
Inspect stored defined_name values in the databaseQuery the database for any records in the action/task tables where the defined_name field contains HTML tags (<script>, <img>, <iframe>, etc.) or JavaScript code patternsAffected if Records exist with unsanitized HTML/JavaScript in the defined_name field that could execute in a browser
-
Review the Overview page rendering of task namesAccess the Overview page in the WISE-DeviceOn web interface and inspect the HTML source to see if user-defined task names are rendered directly without HTML encoding or sanitizationAffected if Task names from the defined_name field are displayed as raw HTML without encoding
-
Check for existing XSS payloads in action/task definitionsExamine any custom actions or tasks defined in the system for suspicious patterns in the defined_name parameter that match XSS attack signaturesAffected if Any defined_name values contain script tags, event handlers (onclick, onerror, etc.), or other XSS vectors
You are affected if WISE-DeviceOn Server version is prior to 5.4 AND the /rmm/v1/action/defined endpoint is accessible AND user-defined task names are rendered without sanitization on the Overview page.
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 includes proper HTML sanitization for user-supplied input in the defined_name field, or implement server-side input validation and output encoding before rendering user-defined task names.
5.4
- Back up all current data and configurations of the WISE-DeviceOn Server
- Obtain the official WISE-DeviceOn Server version 5.4 from Advantech's official download sources (advcloudfiles.advantech.com or docs.deviceon.advantech.com)
- Deploy version 5.4 to replace the existing installation
- After upgrade, verify the /rmm/v1/action/defined endpoint now properly sanitizes the defined_name parameter
- Confirm the Overview page properly handles and encodes task names without executing injected scripts
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-34257 — 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-34257 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