CVE-2025-5382
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 users MFA feature in Devolutions Server 2025.1.7.0 and earlier allows a user with user management permission to remove or change administrators MFA.
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 · moderate confidenceImproper access control vulnerability in Devolutions Server's MFA feature allows users with user management permissions to modify or remove MFA for administrator accounts. This authorization bypass affects versions 2025.1.7.0 and earlier, enabling privilege escalation through unauthorized MFA configuration changes.
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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Devolutions Server versionCheck the installed version of Devolutions Server through the administration console or by inspecting the application binary/version file. Compare against the affected range: versions prior to 2025.1.9.0 (including 2025.1.7.0 and earlier).Affected if The installed version is 2025.1.7.0 or any version prior to 2025.1.9.0
-
Verify if MFA is configuredAccess the Devolutions Server administration console and navigate to the MFA/Global Authentication settings. Determine whether Multi-Factor Authentication has been enabled for the environment.Affected if MFA is enabled and the server version is within the affected range
-
Audit user management permissionsIn the administration console, review all users and groups assigned the 'User Management' or equivalent permission role. Export or document the list of accounts that hold this permission.Affected if Any non-administrator accounts hold user management permissions in an affected version with MFA enabled
-
Review recent MFA configuration changesExamine the system audit logs or security logs for recent modifications to MFA settings, particularly changes targeting administrator accounts. Look for events involving MFA removal or modification performed by non-administrative users.Affected if Audit logs show MFA changes on admin accounts performed by users without full administrator privileges
-
Check for unauthorized admin account modificationsCompare the list of administrator accounts against recent authentication and account modification logs. Identify any admin accounts where MFA was disabled or removed by a user management permission holder.Affected if Any administrator account MFA settings were altered by a user with only user management permissions
You are affected if running Devolutions Server version 2025.1.7.0 or earlier with MFA enabled and any non-administrator holds user management permissions, or if audit logs show unauthorized MFA changes to admin accounts.
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 Devolutions Server to version subsequent to 2025.1.7.0 when patch is available; in the interim, restrict user management permissions to only trusted administrators and audit existing permission assignments.
2025.1.9.0 or later
- 1. Identify the current version of Devolutions Server by checking the About section or using the administration console
- 2. Create a full backup of the Devolutions Server database and configuration files before proceeding with the upgrade
- 3. Download Devolutions Server version 2025.1.9.0 or later from the official Devolutions website
- 4. Run the installer and follow the upgrade wizard instructions, selecting the upgrade option
- 5. After installation completes, verify the new version by checking the About section or administration console
- 6. Log in as an administrator and navigate to the MFA settings to verify the proper access controls are now in place
- 7. Test that users with user management permissions can no longer modify or remove administrator MFA settings
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5382 — 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-5382 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