Vertical Privilege Escalation Techniques
What you'll learn: How attackers elevate their privileges from regular user to administrator by exploiting weaknesses in authorization checks.
The Core Problem
Vertical privilege escalation occurs when an attacker with low-level permissions gains access to high-level functionality. Unlike horizontal escalation (accessing another user's resources at the same privilege level), vertical escalation means jumping up the privilege hierarchy—from regular user to admin, moderator, or superuser.
Think of it like an office building where you have a ground-floor access badge, but you exploit a flaw to reach the executive penthouse suite.
Common Attack Techniques
Direct URL Manipulation
Attackers guess or discover admin URLs like /admin/dashboard or /manager/delete-user and access them directly, bypassing the UI restrictions. Many applications hide admin links but fail to enforce authorization on the actual endpoints.
Parameter Tampering
Changing values like ?role=user to ?role=admin or isAdmin=false to isAdmin=true in requests. If the application trusts client-supplied data without server-side validation, privilege escalation succeeds.
Function-Level Exploitation
Calling administrative API endpoints (like DELETE /api/users/all) that weren't properly locked down, even though the attacker's UI doesn't show these options.
Session Manipulation
Modifying cookies or tokens to include elevated privileges: changing "role":"user" to "role":"administrator" in a JWT when signature validation is weak or missing.
Multi-Step Process Bypass
Skipping intermediate authorization checks by jumping directly to final steps of privileged workflows.
Why It Succeeds
These attacks work when applications rely on presentation-layer security (hiding buttons) instead of enforcing authorization at every function and endpoint on the server side.
Key Takeaway: Vertical privilege escalation exploits missing or weak authorization checks that allow low-privilege users to execute administrative functions by manipulating URLs, parameters, or session data—every privileged operation must verify the user's authorization server-side.