Output Messenger up to 2.0.62 path traversal

Summaryinfo

A vulnerability was found in Output Messenger up to 2.0.62 and classified as critical. Impacted is an unknown function. Executing a manipulation can lead to path traversal. The identification of this vulnerability is CVE-2025-27920. Furthermore, there is an exploit available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability has been found in Output Messenger up to 2.0.62 and classified as critical. This vulnerability affects an unknown code. The manipulation with an unknown input leads to a path traversal vulnerability. The CWE definition for the vulnerability is CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

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.

The advisory is shared for download at srimax.com. This vulnerability was named CVE-2025-27920 since 03/10/2025. The exploitation appears to be easy. Technical details are unknown but an exploit is available. The MITRE ATT&CK project declares the attack technique as T1006.

It is declared as attacked. The vulnerability scanner Nessus provides a plugin with the ID 241199 (Output Messenger < 2.0.63 Multiple Vulnerabilities), which helps to determine the existence of the flaw in a target environment. This issue was added on 05/19/2025 to the CISA Known Exploited Vulnerabilities Catalog with a due date of 06/09/2025:

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Upgrading to version 2.0.63 eliminates this vulnerability.

The vulnerability is also documented in the databases at Zero-Day.cz (998), Tenable (241199) and EUVD (EUVD-2025-13464). Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

• Messaging Software

Name

• Output Messenger

Version

• 2.0.0
• 2.0.1
• 2.0.2
• 2.0.3
• 2.0.4
• 2.0.5
• 2.0.6
• 2.0.7
• 2.0.8
• 2.0.9
• 2.0.10
• 2.0.11
• 2.0.12
• 2.0.13
• 2.0.14
• 2.0.15
• 2.0.16
• 2.0.17
• 2.0.18
• 2.0.19
• 2.0.20
• 2.0.21
• 2.0.22
• 2.0.23
• 2.0.24
• 2.0.25
• 2.0.26
• 2.0.27
• 2.0.28
• 2.0.29
• 2.0.30
• 2.0.31
• 2.0.32
• 2.0.33
• 2.0.34
• 2.0.35
• 2.0.36
• 2.0.37
• 2.0.38
• 2.0.39
• 2.0.40
• 2.0.41
• 2.0.42
• 2.0.43
• 2.0.44
• 2.0.45
• 2.0.46
• 2.0.47
• 2.0.48
• 2.0.49
• 2.0.50
• 2.0.51
• 2.0.52
• 2.0.53
• 2.0.54
• 2.0.55
• 2.0.56
• 2.0.57
• 2.0.58
• 2.0.59
• 2.0.60
• 2.0.61
• 2.0.62

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion