CVE-2025-27920
Srimax Output Messenger Directory Traversal Vulnerability
Srimax Output Messenger
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.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 19 May 2025. US federal agencies were required to remediate it by 9 June 2025.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 1.9%, which is higher than 79.8% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
Frequently asked questions
Is CVE-2025-27920 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2025-27920.
What does CVE-2025-27920 affect?
CVE-2025-27920 affects Srimax Output Messenger. 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.
How severe is CVE-2025-27920?
CVE-2025-27920 is rated HIGH with a CVSS base score of 7.2. EPSS puts the probability of exploitation in the next 30 days at 1.9%, higher than 79.8% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 9 June 2025.
How should organisations respond to CVE-2025-27920?
Apply the vendor patch for Srimax Output Messenger as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.