CVE-2025-6250
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.4.270.0, when wmic.exe is elevated with a full admin token the user can stop the Defendpoint service, bypassing anti-tamper protections. Once the service is disabled, the malicious user can add themselves to Administrators group and run any process with elevated permissions.
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 confidencePrior to version 25.4.270.0, the Defendpoint security product contains a vulnerability where wmic.exe, when elevated with a full admin token, can stop the Defendpoint service. This bypasses anti-tamper protections built into the product, allowing a malicious user to add themselves to the Administrators group and execute processes with elevated permissions.
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.4.270CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/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.
-
Identify installed product versionCheck the version of Beyondtrust Privilege Management for Windows or Defendpoint installed on the system. On Windows, open Programs and Features and look for 'BeyondTrust Privilege Management for Windows' or 'Defendpoint', or use PowerShell: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' | Select-Object DisplayName, DisplayVersionAffected if The displayed version is less than 25.4.270.0 (or 25.4.270)
-
Verify Defendpoint service statusOpen Services console (services.msc) and locate the Defendpoint service, or run: Get-Service -Name 'Defendpoint*' -ErrorAction SilentlyContinueAffected if The service exists and is currently running (the bypass only works against a running service)
-
Confirm wmic.exe accessibilityVerify that wmic.exe exists in the system32 directory (C:\Windows\System32\wmic.exe) and check if non-administrative users can execute it with elevated privileges through existing Privilege Management policiesAffected if Users with full admin tokens can access and execute wmic.exe to stop the service, enabling the bypass
If the installed Beyondtrust Privilege Management for Windows version is below 25.4.270 and the Defendpoint service is running, the environment is vulnerable to this anti-tamper bypass.
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.4.270
Upgrade Defendpoint to version 25.4.270.0 or later to patch the anti-tamper bypass vulnerability. Organizations should also implement least-privilege policies to limit which users can obtain full admin tokens.
25.4.270.0
- Obtain the fixed version 25.4.270.0 of Privilege Management For Windows from the BeyondTrust official download portal or your designated support channel
- Review the BeyondTrust upgrade documentation for Privilege Management For Windows to ensure proper upgrade procedures are followed
- Apply the upgrade to all affected Privilege Management For Windows installations
- Verify the Defendpoint service cannot be stopped by elevated users after the upgrade
- Confirm anti-tamper protections are functioning as expected post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-6250 — 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-6250 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