Broken Access Control
Failure to enforce what authenticated users are allowed to do.
What it is
A category of vulnerabilities where the application does not properly restrict actions or data to authorized users. It spans missing function-level checks, privilege escalation, and unauthorized data access.
Why it matters
Broken access control consistently tops application-security risk rankings and underlies many breaches. Because enforcement gaps are easy to miss, mapping every privileged action to a check is central to assessment.
In practice
A standard user invokes an administrative API endpoint that never verifies their role and the action succeeds.
What to look for
- Users reaching admin pages or functions.
- Changes to role or user fields in requests that succeed.
- Missing checks on API endpoints behind the UI.
Common mistake
Enforcing access in the UI only. The server must check every request.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
- Risk Scoring
Score a vulnerability with CVSS v3.1, or an incident across five dimensions, and see the reasoning behind each number.
- Map and Score
Map real procedures to ATT&CK techniques, then pick the CVSS v3.1 metrics for real vulnerabilities.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Burp Suite Commercial
An intercepting proxy for testing web apps by hand and with its scanner.
-
ZAP Open source
An open source web app scanner and proxy, often run in CI pipelines.
-
Cloudflare WAF Commercial
Blocks common web attacks at the edge while the code gets fixed.
Read next
- Insecure Direct Object Reference: Accessing others' objects by changing an identifier in a request.
- SQL Injection: Injecting SQL through input to manipulate a database query.
- Server-Side Request Forgery: Coercing a server into making attacker-chosen network requests.