CVE-2025-0889
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 · uneditedPrior to 25.2, a local authenticated attacker can elevate privileges on a system with Privilege Management for Windows installed, via the manipulation of COM objects under certain circumstances where an EPM policy allows for automatic privilege elevation of a user process.
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 confidenceA local authenticated attacker can elevate privileges on systems with Privilege Management for Windows versions prior to 25.2 by manipulating COM objects under specific conditions where an EPM (Endpoint Privilege Management) policy permits automatic privilege elevation of user processes.
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< 25.2CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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.
-
Verify Privilege Management for Windows is installedCheck for the presence of BeyondTrust or Privilege Management for Windows software via Programs and Features, or look for the pbgservice.exe process running on the systemAffected if The software is not installed, the vulnerability does not apply
-
Determine the installed version of Privilege Management for WindowsLocate the version information in the installed program directory or via system information tools, then compare the version number to 25.2Affected if The installed version is any version prior to 25.2 (for example, 25.1.x, 24.x, or earlier)
-
Identify configured EPM policiesAccess the Endpoint Privilege Management policy configuration console or exported policy files to review which EPM policies are active on the systemAffected if No EPM policies are defined, the vulnerability cannot be exploited
-
Check if automatic privilege elevation is permittedReview the active EPM policies to determine if any policy allows automatic elevation of user processes without user prompt or confirmationAffected if An EPM policy permits automatic privilege elevation of user processes, making the system vulnerable to the COM object manipulation attack
A system is affected if Privilege Management for Windows versions prior to 25.2 is installed AND an EPM policy configured on the system permits automatic privilege elevation of user processes.
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 · scoped25.2
Upgrade Privilege Management for Windows to version 25.2 or later, and review EPM policies to restrict automatic privilege elevation to minimize attack surface.
25.2
- 1. Verify current Privilege Management for Windows version by checking the installed software or via the Beyond Trust dashboard
- 2. Download Privilege Management for Windows version 25.2 or later from the Beyond Trust support portal
- 3. Test the upgrade in a non-production environment before deploying to production systems
- 4. Apply the upgrade to all systems running versions prior to 25.2
- 5. Verify the upgrade was successful by confirming the new version is installed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0889 — 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-0889 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