# CVE-2025-21293: Active Directory Domain Services Elevation of Privilege Vulnerability

> An attacker can exploit Active Directory Domain Services to elevate privileges on affected Windows systems.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jan 2025
- **Updated:** 9 Jun 2026
- **Also known as:** GHSA-8cgg-rcwg-mmh6

## What is CVE-2025-21293?

CVE-2025-21293 is a high-severity vulnerability in Microsoft Windows 10 1507, published on 14 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Active Directory Domain Services Elevation of Privilege Vulnerability

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2025-21293?

It affects 14 products.


Products: Microsoft Windows 10 1507, Microsoft Windows 10 1607, Microsoft Windows 10 1809, Microsoft Windows 10 21h2, Microsoft Windows 10 22h2, Microsoft Windows 11 22h2, Microsoft Windows 11 23h2, Microsoft Windows 11 24h2, Microsoft Windows Server 2012, Microsoft Windows Server 2016, Microsoft Windows Server 2019, Microsoft Windows Server 2022, Microsoft Windows Server 2022 23h2, Microsoft Windows Server 2025.

## How do I fix CVE-2025-21293?

No fix has been published for CVE-2025-21293 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-21293 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-21293 exists.

Public exploit code:

- CVE-2025-21293 is an elevation of privilege vulnerability in Active Directory Domain Services. It allows "Network Configuration Operators" to execute code with SYSTEM privileges via Windows Performance Counters. Affected Windows versions include Windows 10, 11, and Server. Microsoft patched this in January 2025. Apply updates to mitigate risks. (github_poc): https://github.com/ahmedumarehman/CVE-2025-21293
- Windows Escalate Service Permissions Local Privilege Escalation (metasploit)

## Other vulnerabilities in Microsoft Windows 10 1507

- [CVE-2017-8543](https://insights.sbomify.com/CVE-2017-8543/): Microsoft Windows Search Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2025-33053](https://insights.sbomify.com/CVE-2025-33053/): Microsoft Windows External Control of File Name or Path (high 8.8, exploited in the wild)
- [CVE-2025-33073](https://insights.sbomify.com/CVE-2025-33073/): Microsoft Windows SMB Client Improper Access Control (high 8.8, exploited in the wild)
- [CVE-2024-49039](https://insights.sbomify.com/CVE-2024-49039/): Microsoft Windows Task Scheduler Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2024-43461](https://insights.sbomify.com/CVE-2024-43461/): Microsoft Windows MSHTML Platform Spoofing (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-21293 and fix it if it is affected.

What it is: CVE-2025-21293 is a high-severity vulnerability in Microsoft Windows 10 1507, published on 14 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-21293 exists.

Affected product: Microsoft Windows 10 1507. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-21293/ (Markdown: https://insights.sbomify.com/CVE-2025-21293/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-21293
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-21293
- OSV: https://osv.dev/vulnerability/CVE-2025-21293

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-21293/
Summaries are generated and may contain mistakes; the official description above is the record.