dbcve.org
Devolutions ServerApplication · Devolutions

CVE-2025-6741

HIGH · 7.7 CVSS v3.1 Published 2025-07-22
Fix available
A fix is available. Upgrade to 2025.2.5.0 or later.
See remediation →
83/100
Remediation priority · High
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
Improper access control in secure message component in Devolutions Server allows an authenticated user to steal unauthorized entries via the secure message entry attachment feature This issue affects the following versions : * Devolutions Server 2025.2.2.0 through 2025.2.4.0 * Devolutions Server 2025.1.11.0 and earlier

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

Improper access control in Devolutions Server's secure message component allows authenticated users to access unauthorized entries through the secure message entry attachment feature, enabling unauthorized data exfiltration.

MitigationUpdate to a patched version of Devolutions Server once released; until then, restrict access to the secure message functionality to trusted users only and monitor for anomalous access patterns.

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
Devolutions ServerApplication
Affected:<= 2025.1.11.0>= 2025.2.2.0, < 2025.2.5.0

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
Changed
Confidentiality
High
Integrity
None
Availability
None

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

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. Identify Devolutions Server installation version
    Locate the installed version through the server admin console, registry, or installation logs. In the administration interface, navigate to 'About' or 'System Information' to find the exact version number.
    Affected if The installed version is <= 2025.1.11.0 OR (>= 2025.2.2.0 AND < 2025.2.5.0)
  2. Verify secure message component is active
    Check if the secure message feature is enabled in the Devolutions Server configuration. Navigate to the modules or features settings in the admin panel and confirm whether the secure messaging capability is turned on.
    Affected if The secure message feature is enabled and accessible to users
  3. Review secure message entry attachment permissions
    Inspect the access control settings for the secure message module. Check the user role permissions specifically related to creating, viewing, and attaching entries to secure messages. Look for any entry attachment or data access permissions assigned to user roles.
    Affected if Authenticated users have roles that grant access to the secure message entry attachment feature without proper row-level or entry-level access controls
  4. Audit user access to secure message entries
    Examine the user assignments and access rights for existing secure message entries. Use the administrative reporting tools or database queries to identify which authenticated users can access secure message records that they should not have permission to view.
    Affected if Any authenticated user can access secure message entries or attachments outside their authorized scope

You are affected if Devolutions Server is installed with a version in the affected range AND the secure message component with attachment functionality is enabled for users.

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 2025.2.5.0 or later
Fixed in 2025.2.5.0
Interim mitigation

Update to a patched version of Devolutions Server once released; until then, restrict access to the secure message functionality to trusted users only and monitor for anomalous access patterns.

Recommended fix High confidence

2025.2.5.0

  1. Upgrade Devolutions Server to version 2025.2.5.0 or later
  2. After upgrading, verify that the secure message component properly enforces access controls on entry attachments

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

Fix this in Devolutions Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA2.0 h
22.0 hours of engineering $3,820
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-6741 — 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-6741 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