# CVE-2025-70796: Path traversal in n/a

> Unauthenticated attackers can exploit path traversal in the WTI web management interface to read sensitive system files and configuration data.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jul 2026
- **Updated:** 10 Jul 2026
- **Also known as:** GHSA-v6x3-78p8-29hj

## What is CVE-2025-70796?

CVE-2025-70796 is a high-severity path traversal vulnerability in n/a, published on 10 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An unauthenticated path traversal vulnerability exists in the web management interface of WTI (Wireless Technology, Inc.) version 3.5.0.r 2024/05/24 00:00:00. An unauthenticated attacker can craft malicious HTTP requests containing traversal sequences to access files outside of the intended web root directory. This may allow disclosure of sensitive system files and configuration data

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

## Which versions are affected by CVE-2025-70796?


## How do I fix CVE-2025-70796?

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

## Is CVE-2025-70796 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-70796 and fix it if it is affected.

What it is: CVE-2025-70796 is a high-severity path traversal vulnerability in n/a, published on 10 Jul 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-2025-70796 exists.

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-2025-70796/ (Markdown: https://insights.sbomify.com/CVE-2025-70796/index.md)
```

## Sources

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

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