Security readout for executives and security teams
Plain-English summary
Output Messenger versions before 2.0.63 can mishandle file paths, allowing unauthenticated network attackers to read files outside intended folders. The issue is high severity and is listed in CISA KEV, so organizations using Output Messenger should treat remediation as urgent.
Executive priority
Immediate action is warranted for any organization running Output Messenger. KEV listing means exploitation is confirmed, and the business risk is sensitive file exposure or configuration leakage from messaging infrastructure.
Technical view
CVE-2025-27920 is a CWE-24 path traversal flaw in Srimax Output Messenger before 2.0.63. The CVSS 3.1 score is 7.2, with network access, low complexity, no privileges, no user interaction, changed scope, and low confidentiality and integrity impact.
Likely exposure
Exposure is likely limited to organizations running Srimax Output Messenger before 2.0.63. Risk is higher where Output Messenger services are reachable from untrusted networks. The provided source bundle does not identify affected operating systems, deployment modes, or exact exposed endpoints.
Exploitation context
Active exploitation is supported by CISA KEV status. The provided references also include Microsoft reporting that Marbled Dust leveraged a zero-day in Output Messenger for regional espionage. The bundle does not provide safe evidence for exploit prevalence, targeting scale, or public exploit availability.
Researcher notes
Evidence supports a path traversal class issue with unauthenticated network reachability and confirmed exploitation. The bundle does not include endpoint names, proof-of-concept details, patch diff, or indicators of compromise, so validation should stay focused on versioning, exposure, logs, and vendor guidance.
Mitigation direction
- Upgrade Output Messenger to version 2.0.63 or later.
- Review the vendor advisory for current remediation guidance.
- Restrict Output Messenger access to trusted networks where feasible.
- Prioritize remediation on internet-reachable or partner-accessible deployments.
- Monitor for abnormal file access and configuration leakage indicators.
Validation and detection
- Inventory all Output Messenger deployments and confirm installed versions.
- Identify any instances older than 2.0.63.
- Review server logs for path traversal indicators or unusual file-read errors.
- Check whether exposed instances are listed in vulnerability management tooling.
- Validate remediation by confirming version 2.0.63 or later.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-24: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2025-27920 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.2 (3.1)
- Known Exploited
- Yes
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CISA KEV status
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N3.92.7Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.2HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.srimax.com/products-2/output-messenger/CVE reference
- https://www.outputmessenger.com/cve-2025-27920/CVE reference
- https://www.microsoft.com/en-us/security/blog/2025/05/12/marbled-dust-leverages-zero-day-in-output-messenger-for-regional-espionage/CVE reference · third-party-advisory
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-27920CVE reference · government-resource
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Path Traversal: '../filedir'
Path Traversal: '../filedir' represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.