CVE-2025-27920
Output Messenger before 2.0.63 was vulnerable to a directory traversal attack through improper file path handling. By using ../ sequences in...
Basic Information
- CVE State
- PUBLISHED
- Reserved Date
- March 10, 2025
- Published Date
- May 05, 2025
- Last Updated
- May 21, 2025
- Vendor
- Srimax
- Product
- Output Messenger
- 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.
- Tags
- Score
- 63.72% (Percentile: 98.28%) as of 2025-06-10
- Exploitation
- active
- Automatable
- Yes
- Technical Impact
- partial
- Exploited in the Wild
- Yes (2025-05-12 16:24:56 UTC) Source
cisa
CVSS Scores
CVSS v3.1
7.2 - HIGH
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
EPSS Score
SSVC Information
Exploit Status
References
Known Exploited Vulnerability Information
Source | Added Date |
---|---|
Microsoft Threat Intelligence | 2025-05-12 16:35:47 UTC |
Recent Mentions
CISA Adds Six Known Exploited Vulnerabilities to Catalog
Source: All CISA Advisories • Published: 2025-05-19 12:00:00 UTC
CISA has added six new vulnerabilities to its Known Exploited Vulnerabilities Catalog, based on evidence of active exploitation.
CVE-2025-4427 Ivanti Endpoint Manager Mobile (EPMM) Authentication Bypass Vulnerability
CVE-2025-4428 Ivanti Endpoint Manager Mobile (EPMM) Code Injection Vulnerability
CVE-2024-11182 MDaemon Email Server Cross-Site Scripting (XSS) Vulnerability
CVE-2025-27920 Srimax Output Messenger Directory Traversal Vulnerability
CVE-2024-27443 Synacor Zimbra Collaboration Suite (ZCS) Cross-Site Scripting (XSS) Vulnerability
CVE-2023-38950 ZKTeco BioTime Path Traversal Vulnerability
These types of vulnerabilities are frequent attack vectors for malicious cyber actors and pose significant risks to the federal enterprise.
Binding Operational Directive (BOD) 22-01: Reducing the Significant Risk of Known Exploited Vulnerabilities established the Known Exploited Vulnerabilities Catalog as a living list of known Common Vulnerabilities and Exposures (CVEs) that carry significant risk to the federal enterprise. BOD 22-01 requires Federal Civilian Executive Branch (FCEB) agencies to remediate identified vulnerabilities by the due date to protect FCEB networks against active threats. See the BOD 22-01 Fact Sheet for more information.
Although BOD 22-01 only applies to FCEB agencies, CISA strongly urges all organizations to reduce their exposure to cyberattacks by prioritizing timely remediation of Catalog vulnerabilities as part of their vulnerability management practice. CISA will continue to add vulnerabilities to the catalog that meet the specified criteria.
Zero-day Flaw in Output Messenger Exploited in Espionage Attacks
Source: CyberInsider • Published: 2025-05-12 19:27:36 UTC
Microsoft has uncovered a sophisticated cyberespionage campaign by the threat actor Marbled Dust, which exploited a previously unknown vulnerability in the popular messaging platform Output Messenger. The group, believed to be affiliated with Turkey, has used this zero-day exploit (CVE-2025-27920) since April 2024 to gather intelligence on Kurdish military targets in Iraq. According to Microsoft …
The post Zero-day Flaw in Output Messenger Exploited in Espionage Attacks appeared first on CyberInsider.
Marbled Dust leverages zero-day in Output Messenger for regional espionage
Source: Microsoft Threat Intelligence • Published: 2025-05-12 16:00:00 UTC
Since April 2024, the threat actor that Microsoft Threat Intelligence tracks as Marbled Dust has been observed exploiting user accounts that have not applied fixes to a zero-day vulnerability (CVE-2025-27920) in the messaging app Output Messenger, a multiplatform chat software. These exploits have resulted in collection of related user data from targets in Iraq. Microsoft […]
The post Marbled Dust leverages zero-day in Output Messenger for regional espionage appeared first on Microsoft Security Blog.
Timeline
-
CVE ID Reserved
-
CVE Published to Public
-
Added to KEVIntel