Output Messenger before 2.0.63 was vulnerable to a directory traversal attack through improper file path handling.
Output Messenger by Srimax versions earlier than V2.0.63 are affected. The issue is fixed in V2.0.63.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Actively exploited
- Fix
- Fixed in 2.0.63
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Output Messenger, an instant messaging application, is affected by a directory traversal flaw caused by improper file path handling. An attacker could use crafted path sequences to read sensitive files outside the intended directory, potentially exposing configuration data or other files on the system.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
Output Messenger before 2.0.63 was vulnerable to a directory traversal attack through improper file path handling. By using ../ sequences in parameters, attackers could access sensitive files outside the intended directory, potentially leading to configuration leakage or arbitrary file access.
Timeline
- CVE published
- Added to CISA KEV
CISA has evidence of exploitation in the wild
- CISA remediation deadline
Due date for US federal agencies to patch
- Record last updated
Affected versions
- Srimax Output Messenger
fixed in 2.0.63
References 2
srimax.com
outputmessenger.com
Questions about CVE-2025-27920
What does this mean?
A directory traversal flaw comes from improper file path handling. Attackers can reach sensitive files outside the intended directory, such as configuration files, source code and user data, which could potentially lead to remote code execution.Source: outputmessenger.com
Am I affected, and how do I check?
All Output Messenger versions earlier than V2.0.63 are affected. To check, compare the installed Output Messenger version number with 2.0.63.Source: outputmessenger.com
What should I do about it?
Upgrade Output Messenger to V2.0.63, where the issue is resolved.Source: outputmessenger.com
Is it being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2025-05-19, which means it has evidence of attacks. No public exploit code is tracked.Source: cisa.gov, cve.now feed data