CVE-2025-27920: Srimax Output Messenger Directory Traversal
Srimax Output Messenger · listed in the CISA catalog of actively exploited vulnerabilities since 2025-05-19.
- CVSS v3.1 (CVE record)
- 7.2
- high
- EPSS (exploit probability, 30 days)
- 1.9%
- higher than 80.1% of all CVEs
- Added to CISA KEV
- 2025-05-19
- US federal due date 2025-06-09
- Automatable (CISA SSVC)
- yes
- technical impact: partial
CVE-2025-27920 explained
CVE-2025-27920 is a directory traversal vulnerability in Srimax Output Messenger before 2.0.63. Improper file path handling lets attackers use ../ sequences in parameters to reach files outside the intended directory. CISA lists it as known exploited, so unpatched servers face active risk of configuration leakage or arbitrary file access.
Impact
A remote attacker can read sensitive files outside the intended directory over the network. No authentication and no user interaction are needed, and attack complexity is low. This can expose configuration data or other files. CISA rates it as automatable, meaning it can be exploited at scale, with partial technical impact. The CVSS scope is changed, with low confidentiality and integrity impact. Attackers are known to exploit it.
Who is affected
The CVE record lists Srimax Output Messenger versions < 2.0.63 as affected, which means every version before 2.0.63. The fix is in version 2.0.63. The affected and fixed versions are as published in the CVE record by its CNA (mitre).
Written with AI from the data on this page and checked against it automatically.
Official 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.
CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
CISA notes
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- Srimax Output MessengerAffectedFixed in
- < 2.0.63
- 2.0.63
| Product | Affected | Fixed in |
|---|---|---|
| Srimax Output Messenger |
|
|
How to fix it
- Update to a fixed version: 2.0.63.
- Vendor advisory: srimax.com/products-2/output-messenger
- CISA's deadline for US federal agencies: 2025-06-09 (passed) – a useful benchmark for everyone else, too.
What to do
- Upgrade all Srimax Output Messenger servers to version
2.0.63or later. - Follow the Srimax vendor advisory and apply any mitigations it describes.
- Restrict network access to the Output Messenger server, and avoid exposing it directly to the internet.
- Review server logs for requests containing ../ sequences and check for signs of compromise.
- Rotate credentials and secrets stored in configuration files that may have been exposed.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- Yes – attackers can automate it at scale
- Technical impact
- Partial – limited control or information
Weakness: CWE-24 Path Traversal: '../filedir'
Questions about CVE-2025-27920
- Is CVE-2025-27920 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2025-05-19. US federal agencies had a due date of 2025-06-09. Whether ransomware groups use it is unknown.
- Does an attacker need an account?
- No. The CVSS data shows the attack works over the network with no privileges and no user interaction, and CISA rates it as automatable.
- Which version fixes the issue?
- Output Messenger
2.0.63contains the fix. All earlier versions are affected.
Written with AI from the data on this page and checked against it automatically.
References
Other advisories
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.