# CVE-2018-25365: PCViewer vt1000 Directory Traversal via GET Request

> Unauthenticated attackers can read arbitrary system files via directory traversal in GET requests on PCViewer vt1000 devices.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 May 2026
- **Updated:** 26 May 2026
- **Also known as:** GHSA-2q9f-876r-jm5f

## What is CVE-2018-25365?

CVE-2018-25365 is a high-severity path traversal vulnerability in PCViewer, published on 25 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PCViewer vt1000 contains a directory traversal vulnerability that allows unauthenticated attackers to read arbitrary files by submitting relative path sequences in GET requests. Attackers can use path traversal sequences ../../../../../../../../../../../../etc/passwd to access sensitive system files outside the intended directory.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2018-25365 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-25365 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2018-25365 is a high-severity path traversal vulnerability in PCViewer, published on 25 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-25365 exists.

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

## Sources

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

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