CVE-2025-27920 is an improper path validation vulnerability in Srimax Output Messenger before version 2.0.63, including version 2.0.62. An authenticated attacker can manipulate file-path parameters with directory-traversal sequences to access files outside their intended directories. The flaw can expose configuration files, sensitive user data, or source code, and can be leveraged to upload malicious files into the server startup directory, enabling arbitrary file execution and potentially remote code execution.
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.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this 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.
30 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A directory traversal vulnerability in Srimax Output Messenger that can allow unauthorized access to sensitive files on affected servers.
A directory traversal vulnerability in Output Messenger (version 2.0.62) that allows remote attackers to access or execute arbitrary files. Exploited as a zero-day by the Marbled Dust threat actor for cyber espionage.
An authenticated directory traversal vulnerability in Output Messenger (noted in v2.0.62) that can allow access to or execution of arbitrary files outside intended directories, enabling follow-on compromise via dropped payloads.
A directory traversal vulnerability in Output Messenger (notably v2.0.62) that can be abused (with authentication/compromised credentials) to access sensitive files and enable remote code execution via arbitrary file access/upload into sensitive server directories (e.g., startup directory).
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.