Skip to main content

CVE-2025-27920Srimax Output Messenger Directory Traversal Vulnerability

Patch nowHigh8.8Exploited, CISA due date 2025-06-09EPSS 1.9%, higher than 80% of scored CVEs

CVE-2025-27920 is a path traversal in Srimax Output Messenger, rated high (8.8 on CVSS 3.1).

Why this priority: Exploited in the wild: listed in CISA's KEV catalog.

Published · Updated · NVD status: Analyzed

What it is

Path segments in input let a caller reach files outside the intended folder.

How it is reached

An attacker can exploit it over the network, with an ordinary user account, and nobody has to click anything.

What an attacker gains

A successful attack can read the data it protects, change data or behaviour and take it offline. In practice, this kind of flaw lets an attacker read or write files outside the folders the service meant to expose.

Is it being exploited?

CISA added it to the Known Exploited Vulnerabilities catalog on 2025-05-19: it is being exploited in the wild. It can be exploited automatically, at scale. EPSS estimates a 1.9% chance of exploitation activity in the next 30 days, higher than 80% of scored CVEs.

What to do

  1. Treat it as urgent: it is on CISA's KEV list. CISA's deadline for US federal agencies: 2025-06-09.
  2. Upgrade Srimax Output Messenger to 2.0.63 or later.
  3. Until it is patched, review who holds accounts that can reach it.
  4. Check exposed instances for signs of compromise, not only for the version.

Description from NVD

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.

What this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

  • File storage the service can read or write. The flaw sits between the application and the file system it can reach.

Trust boundaries in play

  • Authenticated network access. An account is needed, so exposure follows who can sign in: customers, partners or staff.
  • Between the application and the file system it can reach. An attacker who crosses it can read or write files outside the folders the service meant to expose.

Questions to answer about your own systems

  • Where does Srimax Output Messenger run in your systems, and at which version?
  • Which of those instances can be reached from the internet or partner networks?
  • What can it reach once compromised: which data stores, secrets and services?

Sources

  • CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
  • Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
  • Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
  • Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.