dbcve.org
Remote Desktop ManagerApplication · Devolutions

CVE-2025-2499

MEDIUM · 5.4 CVSS v3.1 Published 2025-03-26
Fix available
A fix is available. Upgrade to 2024.3.31.0 / 2025.1.26.0 or later.
See remediation →
60/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
Client side access control bypass in the permission component in Devolutions Remote Desktop Manager on Windows. An authenticated user can exploit this flaw to bypass certain permission restrictions—specifically View Password, Edit Asset, and Edit Permissions by performing specific actions. This issue affects Remote Desktop Manager versions from 2025.1.24 through 2025.1.25, and all versions up to 2024.3.29.

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

Client-side access control bypass in the permission component of Devolutions Remote Desktop Manager allows authenticated users to circumvent permission restrictions for View Password, Edit Asset, and Edit Permissions through specific client-side actions.

MitigationApply vendor-provided security patch/upgrade to a version beyond 2025.1.25 or 2024.3.29 to remediate the client-side permission bypass.

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
Remote Desktop ManagerApplication
Affected:< 2024.3.31.0>= 2025.1.24.0, < 2025.1.26.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
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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. Verify Remote Desktop Manager is installed
    Open the application or check installed programs list. In Windows, open Programs and Features or run 'Get-WmiObject -Class Win32_Product' to list installed software. Look for 'Devolutions Remote Desktop Manager'.
    Affected if The application is installed on the system.
  2. Identify installed version number
    In the application, go to Help > About or press F1. Alternatively, on Windows check the registry key: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{GUID}\DisplayVersion or look in the application's installation folder for a version file.
    Affected if Unable to determine version - manual review required.
  3. Compare version against affected ranges
    Match your installed version to these ranges: version < 2024.3.31.0 OR version >= 2025.1.24.0 but < 2025.1.26.0. For example, 2024.3.0.0 through 2024.3.30.x are affected, as are 2025.1.24.0 and 2025.1.25.x.
    Affected if Installed version falls within < 2024.3.31.0 OR >= 2025.1.24.0 AND < 2025.1.26.0.
  4. Confirm permission system is in use
    Check if user accounts, groups, or permission profiles are configured in the application. Look for the Security or Permissions section in the management console, or verify that access control entries exist for entries/folders.
    Affected if The permission/access control feature is enabled and user permissions are defined.

User is affected if Remote Desktop Manager is installed with a version in the ranges < 2024.3.31.0 or >= 2025.1.24.0 to < 2025.1.26.0, and the permission component with user accounts is actively used.

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 2024.3.31.0 / 2025.1.26.0 or later
Fixed in 2024.3.31.02025.1.26.0
Interim mitigation

Apply vendor-provided security patch/upgrade to a version beyond 2025.1.25 or 2024.3.29 to remediate the client-side permission bypass.

Recommended fix High confidence

2025.1.26.0 (or 2024.3.31.0 for legacy branch)

  1. 1. Identify the currently installed version of Remote Desktop Manager from the application
  2. 2. If the installed version is < 2024.3.31.0, upgrade to version 2024.3.31.0 or later
  3. 3. If the installed version is >= 2025.1.24.0 and < 2025.1.26.0, upgrade to version 2025.1.26.0 or later
  4. 4. Download the appropriate fixed version from the official Devolutions website (devolutions.net)
  5. 5. Run the installer with appropriate administrative privileges
  6. 6. Restart the application after installation to ensure the patch is fully applied
  7. 7. Verify the version number reflects the upgraded release

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

Fix this in Remote Desktop Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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