Broken Access Controls are among the most consequential web application attacks, allowing users to access data or perform actions beyond their authorization. Unlike attacks that exploit software flaws alone, these failures abuse legitimate functionality and inadequate permission enforcement.
The consequences can include exposed personal information, account takeover, and unauthorized administrative changes. Understanding how access permissions fail—and how secure development and privacy-focused practices support a broader defense strategy—is essential.
Broken Access Controls occur when a web application fails to properly restrict what authenticated or unauthenticated users can access. Attackers may exploit these weaknesses to view records, change account settings, access administrative functions, or perform actions beyond their assigned permissions.
A common example is changing an account identifier in a URL and receiving another user’s information. This form of insecure direct object reference can expose profiles, invoices, messages, or support tickets when the server trusts user-supplied values without verifying ownership.
Broken Access Controls can also result from predictable administrative URLs, incorrect role checks, or APIs that enforce permissions in the user interface but not on the server. Attackers may bypass hidden buttons or manipulate requests using browser tools.
Effective protection requires server-side authorization checks for every sensitive request. Applications should apply least-privilege permissions, deny access by default, use unpredictable identifiers where appropriate, and test each user role against resources it should not control.