Skip to content

Windows Privilege Escalation

github-actions[bot] edited this page Nov 15, 2026 · 1 revision

Common Windows local privilege escalation vectors, from weak service permissions to kernel exploits. Source: Pentest Laboratories.

Purpose: Covers the path from a standard/low-privileged user to SYSTEM or local Administrator on a single Windows host - the local counterpart to Domain Escalation, scoped to one machine rather than the domain. This is the checklist most directly validated by findings from Windows Build Review; several items here are the exploitation half of misconfigurations that checklist would flag during a passive audit.

Function: The list spans configuration abuse (weak service permissions, unquoted service paths, insecure registry permissions, Group Policy Preferences - all cases of a legitimate Windows feature configured too loosely) and code-level exploitation (DLL injection/hijacking, Token Manipulation, Hot Potato/token impersonation attacks, and specific named vulnerabilities like HiveNightmare and Intel SYSRET). The token manipulation and Hot Potato-family items specifically abuse Windows' privilege/impersonation model rather than any single misconfiguration - they work by tricking a SYSTEM-level process into authenticating to an attacker-controlled listener.

Goal: Establish every independent path from the current user context to SYSTEM/Administrator on the host, and - since several of these are the direct result of specific configuration choices - trace each successful escalation back to a concrete, fixable root cause rather than leaving it as an abstract "privilege escalation possible" finding.

When & how to use this: Run automated enumeration (WinPEAS, PowerUp, or the scripts below) first to shortlist which vectors are actually present, then manually verify and exploit the most promising ones - service misconfigurations and weak registry permissions are typically both more common and lower-risk to test than the named-CVE items like HiveNightmare, which may have narrower applicable version ranges. Cross-reference against Windows Build Review: findings there (weak service permissions, unquoted paths) often predict exactly which items on this list will succeed.


Code Technique Mitre
WPE-01 Stored Credentials NA
WPE-02 Windows Kernel NA
WPE-03 DLL Injection NA
WPE-04 Weak Service Permissions NA
WPE-05 DLL Hijacking NA
WPE-06 Hot Potato NA
WPE-07 Group Policy Preferences NA
WPE-08 Unquoted Service Path NA
WPE-09 Always Install Elevated NA
WPE-10 Token Manipulation NA
WPE-11 Secondary Logon Handle NA
WPE-12 Insecure Registry Permissions NA
WPE-13 Intel SYSRET NA
WPE-14 Print Spooler NA
WPE-15 HiveNightmare NA
WPE-16 Resource Based Constrained Delegation NA

📖 Use These Checklists Responsibly: Authorization is MANDATORY

Attack techniques are powerful - use them ethically and legally.

Repository: ULTIMATE CYBERSECURITY MASTER GUIDE

Maintained by: Pacific Northwest Computers


⚠️ CRITICAL: These are ATTACK TECHNIQUES - Written authorization is REQUIRED ⚠️

⚠️ Unauthorized use is a FEDERAL CRIME with up to 10 years imprisonment ⚠️

⚠️ ALWAYS obtain explicit written authorization before using any technique ⚠️

⭐ Star this repo if you find it useful! ⭐

## Related Files - [README.md](https://github.com/Pnwcomputers/ULTIMATE-CYBERSECURITY-MASTER-GUIDE/wiki/Checklists) - Checklists section index

📄 Source: Checklists/Windows-Privilege-Escalation.md | ✏️ Suggest an edit | ⬅️ Back to Checklists

Clone this wiki locally