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

> Authenticated users can read arbitrary files on the server via path traversal in the Download Template function of TMS Management Console.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jan 2026
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-h8f2-wx3h-xm9j

## What is CVE-2025-69612?

CVE-2025-69612 is a medium-severity path traversal vulnerability in n/a, published on 22 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A path traversal vulnerability exists in TMS Management Console (version 6.3.7.27386.20250818) from TMS Global Software. The "Download Template" function in the profile dashboard does not neutralize directory traversal sequences (../) in the filePath parameter, allowing authenticated users to read arbitrary files, such as the server's Web.config.

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

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

It affects 1 product.


Products: Tmsglobalsoft Tms Management Console.

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

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

## Is CVE-2025-69612 being exploited?

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

Public exploit code:

- A path traversal vulnerability exists in TMS Management Console (github_poc): https://github.com/Cr0wld3r/CVE-2025-69612

## Fix prompt for AI coding agents

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

What it is: CVE-2025-69612 is a medium-severity path traversal vulnerability in n/a, published on 22 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-69612 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-69612/ (Markdown: https://insights.sbomify.com/CVE-2025-69612/index.md)
```

## Sources

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

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