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

> An administrator can read arbitrary files on the server via path traversal in Linkstack, potentially exposing sensitive system or application data.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Sep 2026
- **Updated:** 21 Sep 2026
- **Also known as:** GHSA-pmvm-3wr9-7xq3

## What is CVE-2025-69904?

CVE-2025-69904 is a medium-severity path traversal vulnerability in n/a, published on 11 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Linkstack v4.8.4 and earlier is vulnerable to Path Traversal, which allows an administrator to read arbitrary files on the server by manipulating file path input. Successful exploitation may lead to unauthorized access to sensitive system or application files.

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

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


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

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

## Is CVE-2025-69904 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-69904 is a medium-severity path traversal vulnerability in n/a, published on 11 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-69904 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-2025-69904/ (Markdown: https://insights.sbomify.com/CVE-2025-69904/index.md)
```

## Sources

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

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