Use only the Academy Lab on 127.0.0.1:5177. Do not copy these tests to a public system without explicit written authorization.
Establish the secure baseline
In HTTP Forge select User A as attacker, User B as owner, choose Horizontal IDOR/BOLA, and run AuthZ Matrix on the secure route.
GET http://127.0.0.1:5177/api/resources/resource-bAnonymous 401, User A 403, User B 200, Admin 200. This is expected access control, not a vulnerability.
Test the vulnerable pair
Change only resources to resources-insecure. Keep object, identities, and policy unchanged, then run the matrix again.
GET http://127.0.0.1:5177/api/resources-insecure/resource-bUser A and User B both receive owner data with 200. WSHawk should classify matched foreign access as suspicious.
Confirm a second foreign object
Reverse attacker and owner, change resource-b to resource-a, and run the same policy. Require two confirmed foreign objects before increasing confidence.
User B can read User A’s object on the insecure route.
Save the finding
Create a finding with endpoint, attacker and owner aliases, status codes, sanitized bodies, response hashes, object IDs, policy, timestamp, and replay steps.
Prove it before moving on.
Your finding includes two foreign resources and clearly separates the secure control from the vulnerable behavior.
