Broken object-level authorization
Named by 5 kept items in this workspace.
Search every workspace for Broken object-level authorization. It matches the name as written, so it can find other things that share it.
The items that name it 5
Business-logic flaw on profile updates, confirmed by Evo COS as reachable/exploitable through the running app
Semantic authorization flaw where the flaw is in the relationship between things rather than syntax; rules-based engines are described as genuinely bad at finding it
Root-cause failure where the server does not verify the caller is authorized for the specific object referenced; broader than IDOR
Context-dependent vulnerability where a user can access another user's data (e.g. reading another user's invoice); targeted by AI pentesting
OWASP API Security Top 10 #1 risk; occurs when an application fails to validate whether a user has permission to access a specific object/record, exploited here via sequential integer booking IDs lacking backend authorization checks.
All techniques in this workspace.