dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 9 Jun 2025.
Output MessengerApplication · Srimax

CVE-2025-27920

HIGH · 8.8 CVSS v3.1 Published 2025-05-05
Fix available
A fix is available. Upgrade to 2.0.63 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Output Messenger versions before 2.0.63 contain a directory traversal vulnerability in file path handling. Attackers can use ../ sequences in request parameters to escape the intended directory and access sensitive files anywhere on the filesystem accessible to the application, potentially exposing configuration files, credentials, or other sensitive data.

MitigationUpgrade to Output Messenger version 2.0.63 or later. If upgrading is not immediately feasible, implement strict input validation to reject path traversal sequences (../) in all file-related parameters and enforce path normalization before file operations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Output MessengerApplication
Affected:< 2.0.63

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Output Messenger is installed
    Check for Output Messenger installation by looking for the application in your program files, or check if the service is running (look for processes named OutputMessenger or similar)
    Affected if Output Messenger is present on the system
  2. Identify the installed version
    Access the web interface and navigate to the About or Help section, or check the version information in the application executable or configuration files
    Affected if The version shown is lower than 2.0.63
  3. Verify web interface accessibility
    Attempt to access the Output Messenger web portal via browser at the configured port (default is often port 8081)
    Affected if The web interface is reachable over the network
  4. Confirm vulnerability applicability
    The vulnerability requires the web server component to be running. Check if the Output Messenger web service is enabled and running
    Affected if The web server component is active and the version is below 2.0.63

If Output Messenger is installed with a version lower than 2.0.63 and the web interface is accessible, the environment is vulnerable to directory traversal attacks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.0.63 or later
Fixed in 2.0.63
Interim mitigation

Upgrade to Output Messenger version 2.0.63 or later. If upgrading is not immediately feasible, implement strict input validation to reject path traversal sequences (../) in all file-related parameters and enforce path normalization before file operations.

Recommended fix High confidence

2.0.63

  1. Identify the current installed version of Output Messenger by checking the application or system information
  2. Navigate to the official Output Messenger download page at www.outputmessenger.com or contact the vendor for the latest version
  3. Download version 2.0.63 or the latest stable release that includes the directory traversal fix
  4. Before upgrading, backup all current configuration files, message databases, and user data
  5. Stop the Output Messenger service to ensure a clean upgrade process
  6. Install the new version (2.0.63 or later) by running the installer or applying the update package
  7. Verify the installation completed successfully and the service starts without errors
  8. Confirm the version number has updated to 2.0.63 or later to ensure the vulnerability is patched

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Output Messenger Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,560
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-27920 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-27920 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data