CVE-2018-13861
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 · uneditedTouchpad / Trivum WebTouch Setup V9 V2.53 build 13163 of Apr 6 2018 09:10:14 (FW 303) allows unauthorized remote attackers to reboot or execute other functions via the "/xml/system/control.xml" URL, using the GET request "?action=reboot" for example.
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 confidenceThe Trivum WebTouch Setup V9 firmware V2.53 build 13163 contains an unauthenticated command execution vulnerability in the /xml/system/control.xml endpoint. Attackers can trigger device reboot or execute other system functions by sending a GET request with the 'action=reboot' parameter without any authentication, allowing complete device compromise.
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= 2.53CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 Trivum WebTouch firmware versionAccess the device's web interface or check the system information page, typically found under Settings > System Info or /xml/system/info.xml. Look for a firmware version field showing 'V2.53' or build number '13163'.Affected if The firmware version displayed is exactly V2.53 (build 13163)
-
Confirm the vulnerable endpoint existsAttempt to access the URL path /xml/system/control.xml on the device's web server (e.g., http://[device-ip]/xml/system/control.xml). A successful HTTP response (200 or similar) indicates the endpoint is present.Affected if The /xml/system/control.xml endpoint returns a valid HTTP response (is accessible)
-
Check network exposure of the deviceDetermine if the device's web interface is reachable from untrusted networks. Review firewall rules, NAT configurations, or port forwarding settings that expose HTTP/HTTPS ports (typically 80/443) to the internet or untrusted VLANs.Affected if The device's web interface (port 80/443) is accessible from untrusted networks or the internet without firewall isolation
-
Verify unauthenticated access to control functionsSend a GET request to /xml/system/control.xml with the parameter 'action=reboot' (e.g., http://[device-ip]/xml/system/control.xml?action=reboot). Observe if the device accepts and processes the request without requiring login credentials.Affected if The device executes the action parameter (e.g., reboots) without requiring authentication
The device is affected if it runs Trivum WebTouch V9 firmware V2.53 and the /xml/system/control.xml endpoint is accessible, particularly from untrusted networks, since the vulnerability allows unauthenticated command execution.
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.
From vendor dataApply any available firmware update from the vendor; if no update exists, isolate the device behind a firewall and disable external web access to prevent unauthenticated attacks.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-13861 — 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-2018-13861 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