CVE-2025-2264 is a path traversal information disclosure vulnerability in Sante PACS Server.exe. According to the provided content, an unauthenticated remote attacker can exploit improper path handling to traverse directories and download arbitrary files from the disk drive where the application is installed. The issue allows access to files outside the intended directory scope, resulting in unauthorized disclosure of local file contents.
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 contains a single Metasploit auxiliary module targeting a path traversal vulnerability (CVE-2025-2264) in Sante PACS Server versions up to 4.1.0. The module allows an attacker to retrieve arbitrary files from the server's filesystem by sending a crafted HTTP GET request to the '/assets/' endpoint, using a user-specified traversal depth and file path. The exploit is configurable via options for the base URI, file path, and traversal depth. The module checks for the presence of the vulnerable server and, upon successful exploitation, saves the retrieved file as loot. The code is written in Ruby and is structured according to Metasploit conventions, making it easy to use within the framework. No fake or malicious code is present; the module is a legitimate proof-of-concept for the described vulnerability.
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.
4 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.