dbcve.org
Devolutions ServerApplication · Devolutions

CVE-2025-2278

MEDIUM · 6.5 CVSS v3.1 Published 2025-03-13
Fix available
A fix is available. Upgrade to 2025.1.3.0 or later.
See remediation →
71/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 temporary access requests and checkout requests endpoints in Devolutions Server 2024.3.13 and earlier allows an authenticated user to access information about these requests via a known request ID.

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 an Insecure Direct Object Reference (IDOR) vulnerability in Devolutions Server where the temporary access requests and checkout requests endpoints lack proper authorization checks. An authenticated user can access sensitive information about requests belonging to other users by simply knowing the request ID, due to missing validation that the requesting user owns or has permission to access the specific request.

MitigationUpgrade to Devolutions Server version 2024.3.14 or later which implements proper authorization checks. Alternatively, add server-side validation to verify the authenticated user has permission to access the requested resource before returning any information.

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.3.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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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. Check Devolutions Server installed version
    Open the Devolutions Server Management Console or check the installed version through the About section in the web interface. You can also check the Windows Programs and Features list for 'Devolutions Server' to see the installed version number.
    Affected if The installed version is below 2025.1.3.0 (or below 2024.3.14 if that branch also received the fix)
  2. Verify temporary access requests feature is in use
    Check if any users have submitted temporary access requests in the system. Log into the Devolutions Server web interface and navigate to the Administration or Sessions panel to look for temporary access request records or check the request logs.
    Affected if Temporary access requests exist in the system and the server version is vulnerable
  3. Verify checkout requests feature is in use
    Check if any password checkout requests have been created. Look in the Vault or Passwords section of the Devolutions Server interface for checkout request entries, or check the audit logs for checkout-related activity.
    Affected if Checkout requests exist in the system and the server version is vulnerable
  4. Check for evidence of unauthorized access
    Review Devolutions Server audit logs for any access patterns where a user accessed request IDs that do not belong to them. Look for anomalies in the request access logs, particularly where request IDs appear in sequence or where users accessed requests outside their expected scope.
    Affected if Audit logs show users accessing request IDs outside their own requests, indicating potential exploitation

You are affected if your Devolutions Server version is below 2025.1.3.0 and the temporary access requests or checkout requests features are actively used in your environment.

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.1.3.0 or later
Fixed in 2025.1.3.0
Interim mitigation

Upgrade to Devolutions Server version 2024.3.14 or later which implements proper authorization checks. Alternatively, add server-side validation to verify the authenticated user has permission to access the requested resource before returning any information.

Recommended fix High confidence

2025.1.3.0

  1. Back up the current Devolutions Server installation and database before upgrading
  2. Download Devolutions Server version 2025.1.3.0 or later from the official Devolutions website
  3. Follow the vendor's documented upgrade procedure to apply the update
  4. Verify the upgrade was successful by checking the server version
  5. Confirm that temporary access requests and checkout requests now properly enforce access controls

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
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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