Skip to main content
Mallory
HighExploited in the wildCISA KEVVulnerability

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

Published May 5, 2025 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.8High · v3.1
EPSS1.9%80th percentile
CISA KEVYesAdded May 19, 2025
In the wildActivePer CISA KEV
Vendor
Srimax
IdentifiersCVE-2025-27920CWE-22 · Improper Limitation of a Pathname…

CVE-2025-27920 is a directory traversal vulnerability in Srimax Output Messenger versions before 2.0.63, including version 2.0.62. Improper handling of file-path parameters permits access to files outside intended directories. Authenticated attackers can also manipulate upload destinations to place malicious files in the server's startup directory, facilitating arbitrary code execution. Marbled Dust, also known as Sea Turtle, exploited the vulnerability in espionage operations beginning in April 2024.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Exploitation can expose configuration information, sensitive user data, source code, and user communications. Malicious uploads into the server's startup directory can facilitate code execution and backdoor deployment. Server compromise can enable access to every user's communications, user impersonation, credential compromise, unauthorized access to internal systems, and operational disruption. Observed exploitation campaigns included command execution and data exfiltration through deployed backdoors.

Mitigation

If you can’t patch tonight, do this now.

Enforce access controls and multi-factor authentication, and deploy intrusion detection to reduce account-compromise risk and identify malicious activity. These measures do not correct the directory traversal flaw and should not replace upgrading to a patched version.

Remediation

Patch, then assume compromise.

Upgrade Output Messenger to version 2.0.63 or a later patched release. Version 2.0.63, released in December 2024, addresses CVE-2025-27920. Deployments that remained unpatched were targeted after the fix became available.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
SrimaxOutput Messengerapplication
FAQ

Frequently asked questions

Is CVE-2025-27920 exploited in the wild?
Yes. As of Oct 9, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on May 19, 2025.
Is there a public exploit for CVE-2025-27920?
As of Oct 9, 2026, Mallory has found no public exploit for CVE-2025-27920.
Is there a patch for CVE-2025-27920?
Upgrade Output Messenger to version 2.0.63 or a later patched release. Version 2.0.63, released in December 2024, addresses CVE-2025-27920.
What products are affected by CVE-2025-27920?
Srimax Output Messenger.
How severe is CVE-2025-27920?
CVE-2025-27920 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 1.9% (80th percentile) as of Oct 9, 2026.
Activity feed

Recent activity

33 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+7 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence4Every report linking this CVE to a named adversary.
Associated malware9Malware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity22Community discussion across Reddit, Mastodon, and other social sources.