dbcve.org
Devolutions ServerApplication · Devolutions

CVE-2025-12808

MEDIUM · 6.5 CVSS v3.1 Published 2025-11-06
Fix available
A fix is available. Upgrade to 2025.2.17.0 / 2025.3.6.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 Devolutions allows a View-only user to retrieve sensitive third-level nested fields, such as password lists custom values, resulting in password disclosure. This issue affects the following versions : * Devolutions Server 2025.3.2.0 through 2025.3.5.0 * Devolutions Server 2025.2.15.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 · high confidence

Improper access control in Devolutions Server allows View-only users to retrieve sensitive third-level nested fields (password lists custom values), bypassing intended permission restrictions and exposing password data to users who should have read-only, non-sensitive access.

MitigationUpgrade to Devolutions Server version 2025.3.6.0 or later. If immediate patching is not possible, review and restrict View-only user role permissions to prevent access to password-related entry fields.

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.2.17.0>= 2025.3.2.0, < 2025.3.6.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. Identify the installed Devolutions Server version
    Access the server administration console or check the application version information typically found in Help > About or server logs
    Affected if The version number is less than 2025.2.17.0 OR between 2025.3.2.0 and 2025.3.5.0 (inclusive)
  2. Locate View-only role configuration
    Navigate to Administration > Security > Roles or User Management in the Devolutions Server interface to find the View-only role definition
    Affected if View-only role exists and is assigned to users in the environment
  3. Identify password entries with custom fields
    Search for password entries or password lists that contain custom fields, particularly nested third-level fields containing sensitive values
    Affected if Password entries with custom values exist in the vault/repository
  4. Test View-only user access to password custom fields
    Log in with a View-only assigned user account and attempt to navigate to or expand password entries to view their custom field values
    Affected if View-only users can retrieve or view password list custom values (third-level nested fields) that should be restricted
  5. Confirm version falls within affected range
    Compare your identified version against the affected ranges: < 2025.2.17.0 or >= 2025.3.2.0 but < 2025.3.6.0
    Affected if The installed version matches either range and View-only users can access password custom values

If Devolutions Server version is in the affected range (below 2025.2.17.0 or between 2025.3.2.0-2025.3.5.0) AND View-only users can retrieve password list custom values, the environment is vulnerable to CVE-2025-12808.

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.17.0 / 2025.3.6.0 or later
Fixed in 2025.2.17.02025.3.6.0
Interim mitigation

Upgrade to Devolutions Server version 2025.3.6.0 or later. If immediate patching is not possible, review and restrict View-only user role permissions to prevent access to password-related entry fields.

Recommended fix High confidence

2025.2.17.0 (for 2025.2.x branch) or 2025.3.6.0 (for 2025.3.x branch)

  1. Identify your current Devolutions Server version by checking the product UI or system information
  2. If running version 2025.2.x (2025.2.15.0 or earlier), upgrade to version 2025.2.17.0 or later
  3. If running version 2025.3.2.0 through 2025.3.5.0, upgrade to version 2025.3.6.0 or later
  4. After upgrading, verify that View-only users can no longer access third-level nested fields such as password lists custom values
  5. Test that proper access controls are enforced for sensitive credential data

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

Fix this in Devolutions Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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