# CVE-2018-13861: Missing authorization in n/a

> Unauthorized remote attackers can reboot or execute functions on Trivum WebTouch Setup devices via unauthenticated GET requests to a specific URL.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jul 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-j8mx-86pp-hqpr

## What is CVE-2018-13861?

CVE-2018-13861 is a critical missing authorization vulnerability in n/a, published on 17 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Touchpad / 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.

## Which versions are affected by CVE-2018-13861?

It affects 1 product.


Products: Trivum Webtouch Setup V9 Firmware.

## How do I fix CVE-2018-13861?

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

## Is CVE-2018-13861 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-13862](https://insights.sbomify.com/CVE-2018-13862/): Auth bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-13861 and fix it if it is affected.

What it is: CVE-2018-13861 is a critical missing authorization vulnerability in n/a, published on 17 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-13861 in the wild and no public exploit code.

Affected product: n/a. 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-2018-13861/ (Markdown: https://insights.sbomify.com/CVE-2018-13861/index.md)
```

## Sources

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

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