One test user could open another test user’s order.
- The goal
Could test account A reach an order belonging to test account B?
- Check the boundary
The agent starts with the order view available to account A.
- A defense holds
That page blocks access to the other account’s order.
- Change the approach
The agent checks another order-view route inside the same approved test scope.
- The illustrated outcome
This second route returns account B’s synthetic order. The permission check is inconsistent.
See the synthetic example
- Expected behavior
- Account A can view only its own orders. Every route must enforce the same permission check.
- Illustrated result
- The second route exposes a synthetic order belonging to account B. This is made-up example data, not captured customer evidence.
- What to fix first
- Check on the server that every requested order belongs to the signed-in user. Add a test that rejects access from another account.
- Assessment limit
- This example covers one workflow. It is not a security verdict on the whole product.
Your paid report, in plain language
- Outcome and impact: what the agent could do.
- Evidence and first fixes: what your developer can verify and change.
- Scope and limits: what we tested and which defenses held.
