CVE-2025-4433
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 · uneditedImproper access control in user group management in Devolutions Server 2025.1.7.0 and earlier allows a non-administrative user with both "User Management" and "User Group Management" permissions to perform privilege escalation by adding users to groups with administrative privileges.
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 confidenceDevolutions Server versions 2025.1.7.0 and earlier contain an improper access control vulnerability in user group management that allows non-administrative users with both 'User Management' and 'User Group Management' permissions to perform privilege escalation by adding users to groups with administrative privileges.
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< 2025.1.9.0CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Check Devolutions Server versionLocate the installed Devolutions Server version in the application UI under Help > About, or check the installation directory for version information. Compare the installed version to the affected range: versions earlier than 2025.1.9.0Affected if The installed version is 2025.1.7.0 or earlier, or any version below 2025.1.9.0
-
Identify users with User Management permissionIn the Devolutions Server administrative console, navigate to the user or role management section. Review which users or roles are assigned the 'User Management' permission.Affected if Non-administrative users have the 'User Management' permission assigned
-
Identify users with User Group Management permissionIn the administrative console, review the permissions assigned to users or roles. Locate those with 'User Group Management' permission.Affected if Non-administrative users have the 'User Group Management' permission assigned
-
Determine if any user has both permissionsCross-reference the users identified in steps 2 and 3. Identify any non-administrative user account that possesses BOTH 'User Management' AND 'User Group Management' permissions simultaneously.Affected if A non-administrative user has both 'User Management' and 'User Group Management' permissions
-
Review administrative privilege groupsIn the user group management section, identify groups that grant administrative privileges or elevated access rights within Devolutions Server.Affected if Groups with administrative privileges exist in the system that could be targeted for privilege escalation
A user is affected if their Devolutions Server version is below 2025.1.9.0 AND a non-administrative user account possesses both 'User Management' and 'User Group Management' permissions, creating the conditions for privilege escalation.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2025.1.9.0
Upgrade to Devolutions Server version 2025.1.8.0 or later which addresses this authorization bypass, or implement additional access control checks to prevent non-administrative users from modifying group memberships that grant administrative privileges.
2025.1.9.0
- Obtain the latest Devolutions Server 2025.1.9.0 installation package from the official Devolutions download portal or your licensed distribution channel
- Review the official Devolutions Server 2025.1.9.0 release notes for any specific upgrade prerequisites or migration requirements
- Create a complete backup of the current Devolutions Server database and configuration
- Test the upgrade in a non-production environment before deploying to production
- Execute the upgrade following Devolutions standard upgrade procedures for your deployment type (typically running the installer and following prompts)
- Verify the upgrade completed successfully by checking the version in the administration console
- Confirm that user group management permissions now properly restrict non-administrative users from adding users to administrative privilege groups
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-4433 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-4433 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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