Order accessible by another customer
- Scope
- Example Store · Orders API
- Evidence
- Customer A can retrieve Customer B's order.
- Required fix
- Check ownership in application code.
Read sample report
Scope and method
A fictional grey-box API test with two test accounts, showing how a report sets out scope and evidence.
Reproduction evidence
Sign in as customer-a and request an order owned by customer-b.
GET /api/orders/order-b07
Authenticated account: customer-a
HTTP/1.1 200 OK
{
"id": "order-b07",
"ownerId": "customer-b"
}Business impact
A signed-in customer can read another customer's order: unauthorized disclosure. Changing or deleting the order was not shown.
Remediation and protection
Bind the lookup to the signed-in owner and review the shared-team access policy. Defend can log this request but not block it, because a rule cannot see sessions or the database to decide who owns an order.
Verification
Replayed against patched staging with Defend off: 404 for cross-customer access, 200 for the legitimate owner and 401 for a signed-out request. Shared-team access still needs a policy decision.
Review and delivery
A named consultant approves every Assess finding before it reaches you. Your engagement sets the scope, access, delivery date and retest terms. The report supports your audit; acceptance is your auditor’s decision.
Illustrative sample data. No customer information.