Course contentsShow
← Security
Lesson 805 of 3,05217. Web Security - Authorization and Access ControlFree lesson

Missing Function-Level Access Control

Exploiting endpoints that fail to verify if the user is authorized to perform administrative or privileged functions.

Missing Function-Level Access Control

What you'll learn: How attackers exploit unprotected administrative functions by directly accessing endpoints that don't verify authorization.

The Vulnerability

Missing Function-Level Access Control occurs when an application fails to verify whether the current user has permission to perform a privileged action before executing it. The server assumes that hiding links or buttons in the UI is enough protection—but attackers don't need buttons. They can craft HTTP requests directly to administrative endpoints.

Think of it like a hotel: just because the staff elevator button isn't on the guest floor panel doesn't mean guests can't press "Staff Only" buttons if they find the elevator controls. If no one checks badges when the door opens, unauthorized people get access.

Common Scenarios

An application might check your role when rendering the admin dashboard, but the underlying API endpoints (/api/deleteUser, /api/promoteModerator) don't verify permissions. An attacker discovers these URLs through:

  • Browser developer tools watching network traffic
  • Directory enumeration or guessing common patterns
  • Leaked documentation or JavaScript files

They then call these endpoints directly, bypassing the UI entirely.

The Core Problem

The vulnerability exists when:

  1. Authorization checks happen only in the presentation layer (UI/frontend)
  2. Backend endpoints trust that only authorized users will call them
  3. No server-side verification of user roles/permissions occurs before executing privileged functions

Real-World Impact

Attackers gaining access to admin functions can delete data, modify system configurations, escalate their own privileges, or compromise other users—all because the server forgot to ask: "Should this user be allowed to do this?"

Key Takeaway: Every privileged endpoint must independently verify the user's authorization on the server side—UI restrictions alone provide zero security.