dbcve.org
Devolutions ServerApplication · Devolutions

CVE-2025-0691

MEDIUM · 5.0 CVSS v3.1 Published 2025-06-05
Fix available
A fix is available. Upgrade to after 2025.1.10.0 or later.
See remediation →
56/100
Remediation priority · Elevated
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 permissions component in Devolutions Server 2025.1.10.0 and earlier allows an authenticated user to bypass the "Edit permission" permission by bypassing the client side validation.

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 · high confidence

This is a client-side authorization bypass in Devolutions Server's permissions component. An authenticated user can bypass the 'Edit permission' permission by manipulating client-side validation checks that should be enforced server-side. The vulnerability allows unauthorized modification of permissions that the user should not have access to edit.

MitigationImplement server-side authorization checks that enforce permission validation on the backend, removing trust for client-side validation. Upgrade to Devolutions Server version 2025.1.11.0 or later which addresses this issue.

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.10.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
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/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 installed Devolutions Server version
    Access the Devolutions Server administration interface and navigate to the About or System Information section to view the current software version. Alternatively, check the application's installation metadata or version file if accessible.
    Affected if The installed version is 2025.1.10.0 or any earlier version within the 2025.1.x release line.
  2. Confirm authentication mechanism is enabled
    Verify that user authentication is configured and active on the Devolutions Server instance. This includes local user accounts, AD/LDAP integration, or other authentication providers.
    Affected if User authentication is enabled, as the vulnerability requires an authenticated user to exploit the client-side validation bypass.
  3. Verify permissions management feature is accessible
    Log in as a standard user and navigate to the permissions or access control section of the Devolutions Server interface. Check if the user can access any permission management or role configuration screens.
    Affected if The authenticated user has access to any permissions management interface, as this is the component where the client-side validation bypass occurs.
  4. Check for Edit permission capability
    Within the permissions management interface, attempt to locate or modify permission entries for other users or groups. Observe whether the interface permits entry into permission modification screens.
    Affected if The user can reach screens related to editing permissions, even if they lack the formal 'Edit permission' authorization grant.

A user is affected if running Devolutions Server version 2025.1.10.0 or earlier with authenticated users who have any access to the permissions management component.

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 a release after 2025.1.10.0
Interim mitigation

Implement server-side authorization checks that enforce permission validation on the backend, removing trust for client-side validation. Upgrade to Devolutions Server version 2025.1.11.0 or later which addresses this issue.

Recommended fix Moderate confidence

2025.1.11.0 or later

  1. 1. Identify the current installed version of Devolutions Server
  2. 2. Navigate to the official Devolutions download page at devolutions.net
  3. 3. Download the latest stable version of Devolutions Server (version 2025.1.11.0 or later)
  4. 4. Review the release notes to confirm CVE-2025-0691 is addressed
  5. 5. Perform a full backup of the Devolutions Server database and configuration
  6. 6. Stop the Devolutions Server service
  7. 7. Install the downloaded update following standard upgrade procedures
  8. 8. Start the Devolutions Server service
Caveat Review release notes for any configuration changes required during upgrade

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

Fix this in Devolutions Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
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,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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