# CVE-2025-27920: Srimax Output Messenger Directory Traversal

> Attackers can access sensitive files outside the intended directory via directory traversal, leading to configuration leakage or arbitrary file access.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Yes, since 19 May 2025 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 May 2025
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-66q6-24vw-2g98

## What is CVE-2025-27920?

CVE-2025-27920 is a high-severity path traversal vulnerability in Srimax Output Messenger, published on 5 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-24 (Path Traversal: '../filedir')

## Which versions are affected by CVE-2025-27920?

It affects 1 product.


Products: Srimax Output Messenger.

## How do I fix CVE-2025-27920?

No fix has been published for CVE-2025-27920 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 9 Jun 2025.

## Is CVE-2025-27920 being exploited?

Yes. Attackers have exploited CVE-2025-27920 in the wild since at least 19 May 2025.

## Other vulnerabilities in Srimax Output Messenger

- [CVE-2025-27921](https://insights.sbomify.com/CVE-2025-27921/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-27920 and fix it if it is affected.

What it is: CVE-2025-27920 is a high-severity path traversal vulnerability in Srimax Output Messenger, published on 5 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2025-27920 in the wild since at least 19 May 2025.

Affected product: Srimax Output Messenger. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-27920/ (Markdown: https://insights.sbomify.com/CVE-2025-27920/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-27920
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-27920
- OSV: https://osv.dev/vulnerability/CVE-2025-27920

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-27920/
Summaries are generated and may contain mistakes; the official description above is the record.