CVE-2018-25113 is an unauthenticated path traversal vulnerability in Dicoogle PACS Web Server 2.5.0, and possibly earlier versions. The /exportFile endpoint insufficiently restricts file-path input supplied through the UID parameter, enabling a remote attacker to craft a request that reads arbitrary files accessible to the web server process.
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 directory traversal vulnerability (CVE-2018-25113) in the Dicoogle PACS Web Server v2.5.0 (and possibly earlier) on Windows. The module exploits the vulnerability by sending a crafted HTTP GET request to the /exportFile endpoint, using the UID parameter to inject directory traversal sequences and read arbitrary files from the server. The exploit is unauthenticated and allows the attacker to specify the file path and traversal depth. The retrieved file is saved locally. The code is written in Ruby and is structured as a standard Metasploit module, with configurable options for the target port, file path, and traversal depth. The main entry point is the run_host function, which performs the exploitation logic.
3 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.