# CVE-2025-13008: Session Token Disclosure in M-Files Web

> An authenticated attacker can capture session tokens of other users via M-Files Web, potentially leading to account takeover.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 19 Dec 2025
- **Updated:** 23 Feb 2026
- **Also known as:** GHSA-829c-jpvx-vfrv

## What is CVE-2025-13008?

CVE-2025-13008 is a high-severity vulnerability in M-Files Server, published on 19 Dec 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

An information disclosure vulnerability in M-Files Server before versions 25.12.15491.7, 25.8 LTS SR3, 25.2 LTS SR3 and 24.8 LTS SR5 allows an authenticated attacker using M-Files Web to capture session tokens of other active users.

Weakness: CWE-359 (Exposure of Private Personal Information to an Unauthorized Actor)

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


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

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

## Is CVE-2025-13008 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-13008 is a high-severity vulnerability in M-Files Server, published on 19 Dec 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-13008 in the wild and no public exploit code.

Affected product: M-Files Server. 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-13008/ (Markdown: https://insights.sbomify.com/CVE-2025-13008/index.md)
```

## Sources

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

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