CVE-2025-5964 is a path traversal vulnerability in an API endpoint of M-Files Server affecting versions before 25.6.14925.0. The flaw allows an authenticated user to supply crafted path input that traverses outside the intended directory scope, resulting in unauthorized read access to files on the server. Based on the available information, the issue is limited to file read via the vulnerable API endpoint; no specific vulnerable function or handler name is provided in the source content.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository provides a proof-of-concept (PoC) exploit in C for a suspected path traversal vulnerability (CVE-2025-5964) in M-Files version 25.6.14925.0. The main file, 'exploit.c', is a command-line tool that takes a target URL and attempts to read sensitive files (such as /etc/passwd) from the server by injecting various path traversal payloads into three REST API query parameters: 'q', 'o', and 'd' of the '/REST/objects.aspx' endpoint. The tool rotates User-Agent strings to evade basic filtering, analyzes HTTP responses for UNIX file markers, and flags potential LFI hits. The exploit is a PoC and not a confirmed working exploit, as the author did not have access to a real M-Files instance for testing. The code is well-commented, includes basic error handling, and is intended for research and authorized security testing only. The repository contains three files: a license, a README with detailed usage instructions, and the main exploit code. No hardcoded IPs or domains are present; the target URL is supplied by the user at runtime.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.