CVE-2025-12485
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 privilege management during pre-MFA cookie handling in Devolutions Server allows a low-privileged authenticated user to impersonate another account by replaying the pre-MFA cookie.This does not bypass the target account MFA verification step. 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 confidenceImproper privilege management in Devolutions Server allows a low-privileged authenticated user to capture and replay a pre-MFA cookie to impersonate another user account. The vulnerability exists in the pre-MFA cookie handling logic, which does not properly bind the cookie to the authenticated session or validate that the cookie is being used by its original owner.
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.2.17.0>= 2025.3.2.0, < 2025.3.6.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 through the administration console, Windows Programs and Features, or by querying the service information. This is typically found in the About section of the web interface or the Windows installed programs list.Affected if The installed version is either below 2025.2.17.0, or between 2025.3.2.0 and 2025.3.5.0 inclusive.
-
Verify if pre-MFA cookie authentication is in useDetermine whether the authentication flow involves a pre-MFA cookie by reviewing the authentication configuration and login flow in the Devolutions Server administration panel. This cookie is used during the transition between credential validation and MFA enforcement.Affected if Pre-MFA cookie handling is active in the authentication workflow, which is the default behavior in unpatched versions.
-
Review authentication logs for duplicate cookie usageExamine the Devolutions Server authentication and audit logs for entries showing the same pre-MFA cookie being used from different sessions or IP addresses in short succession. Look for authentication events with identical session identifiers or cookie values.Affected if Duplicate or replayed pre-MFA cookies are detected in the logs, indicating exploitation attempts or successful impersonation.
-
Check for unexpected user identity transitionsReview session and audit logs for cases where a low-privileged user account suddenly shows actions or permissions associated with a different target user account, occurring before the MFA challenge step.Affected if User identity transitions are logged that occur between credential validation and MFA completion without corresponding re-authentication.
A user is affected if their Devolutions Server version falls within the vulnerable ranges and evidence of pre-MFA cookie replay or unauthorized identity impersonation is found in authentication logs.
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.2.17.02025.3.6.0
Apply the vendor-provided patch for CVE-2025-12485 to fix the pre-MFA cookie handling. Review authentication session management to ensure cookies are bound to user sessions and cannot be replayed across accounts.
2025.2.17.0 or later for 2025.2.x branch; 2025.3.6.0 or later for 2025.3.x branch
- 1. Identify the currently installed Devolutions Server version by checking the About or Version section in the administration console
- 2. If running version 2025.2.x and below 2025.2.17.0, plan upgrade to version 2025.2.17.0 or later in the 2025.2.x branch
- 3. If running version 2025.3.2.0 through 2025.3.5.0, plan upgrade to version 2025.3.6.0 or later in the 2025.3.x branch
- 4. Review Devolutions Server upgrade documentation for backup and migration requirements
- 5. Perform a full backup of the Devolutions Server database and configuration before upgrading
- 6. Apply the upgrade following vendor documentation, ensuring the pre-MFA cookie handling security fix is included
- 7. After upgrade, verify that pre-MFA cookies are properly invalidated and that privilege escalation is no longer possible
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,536.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-12485 — 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-12485 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