Vulnerability in Srimax Output Messenger
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 parameters, attackers could access sensitive files outside the intended directory, potentially leading to configuration leakage or arbitrary file access.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 7.2 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N.
EPSS exploit prediction
EPSS: 0.019 (78.9th percentile), scored .
Low probability of exploitation in the next 30 days, but still tracked. 79th percentile — 78.9% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.019 · newest: 0.019 · change: +0.000
Affected products
- Srimax Output Messenger — versions 0
- Srimax Output Messenger
Weakness classification (CWE)
CISA KEV (Known Exploited Vulnerabilities)
This CVE is on the CISA KEV catalog, added on . CISA KEV inclusion means CISA has confirmed in-the-wild exploitation; US federal agencies are required to remediate within a published due date.
BOD 22-01 due date: .
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.
Public proof-of-concept exploits
References
- www.srimax.com/products-2/output-messenger/ (Product)
- www.outputmessenger.com/cve-2025-27920/ (Vendor Advisory)
- 134c704f-9b21-4f2e-91b3-4a467353bcc0 (US Government Resource)
- 134c704f-9b21-4f2e-91b3-4a467353bcc0 (Mitigation, Third Party Advisory)
Frequently asked questions
- What is CVE-2025-27920?
- CVE-2025-27920 is a high-severity vulnerability in Srimax Output Messenger, classified under CWE-24. CVSS score: 7.2/10. Published 2025-05-05.
- How severe is CVE-2025-27920?
- High severity. CVSS v3 base score is 7.2 out of 10.
- Is CVE-2025-27920 known to be exploited?
- Yes. CVE-2025-27920 is listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-05-19), indicating it is being actively exploited. 3 public proof-of-concept repositories are indexed.