# CVE-2023-3425: CVE-2023-3425: Out-of-Bounds memory read

> An unauthenticated attacker can read restricted memory bytes via an out-of-bounds read in M-Files Server, potentially exposing sensitive data.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Aug 2023
- **Updated:** 23 Feb 2026
- **Also known as:** GHSA-fx24-f32v-56xf

## What is CVE-2023-3425?

CVE-2023-3425 is a medium-severity vulnerability in M-Files Server, published on 25 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Out-of-bounds read issue in M-Files Server versions below 23.8.12892.6 and LTS Service Release Versions before 23.2 LTS SR3 allows unauthenticated user to read restricted amount of bytes from memory.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2023-3425?

It affects 1 product.


Products: M-Files Classic Web.

## How do I fix CVE-2023-3425?

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

## Is CVE-2023-3425 being exploited?

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

## Other vulnerabilities in M-Files Server

- [CVE-2023-3406](https://insights.sbomify.com/CVE-2023-3406/): Path traversal issue in M-Files Classic Web (high 7.7)
- [CVE-2023-2325](https://insights.sbomify.com/CVE-2023-2325/): Stored XSS Vulnerability in M-Files Classic Web (high 7.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-3425 and fix it if it is affected.

What it is: CVE-2023-3425 is a medium-severity vulnerability in M-Files Server, published on 25 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-3425 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-2023-3425/ (Markdown: https://insights.sbomify.com/CVE-2023-3425/index.md)
```

## Sources

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

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