Access Control for Bug Bounty Hunters
Access control bugs let a user do or see what they should not. They include insecure direct object references where changing an ID exposes another account, missing function-level checks, privilege escalation, and authentication flaws such as weak password reset, session fixation or bypassed multi-factor checks. They are common and often high impact.
Stage: Vulnerability Classes · Part of the Bug Bounty Hunter roadmap · Last reviewed 19 November 2026
What to learn in Access Control
- Test for IDOR by swapping identifiers between two test accounts
- Check whether a low-privilege user can call admin endpoints
- Review a password reset flow for token reuse or predictability
- Find business logic flaws such as skipping a payment step
- Explain broken authentication versus broken authorisation
Access Control interview questions
What is an IDOR and how do you test for it?
An insecure direct object reference occurs when an app uses a user-supplied identifier without checking ownership. Log in as two accounts, capture a request for one account's object, and replay it with the other account's session. If data returns, access control is broken.
What is the difference between authentication and authorisation bugs?
Authentication bugs concern proving who you are, such as weak login or reset flows. Authorisation bugs concern what an authenticated identity may do, such as reading another user's records. Both matter, but authorisation flaws are more often found in APIs.
Where Access Control fits in the Bug Bounty Hunter roadmap
Access Control belongs to the Vulnerability Classes stage (intermediate level), which takes about 33 hours. What to look for.
Other units in this stage
Back to the full Bug Bounty Hunter roadmap