Changing one header lets a tenant admin read another tenant’s users
What we found
The SaaS app read the tenant ID from a request header set by the front end, and the API trusted it without checking it against the signed-in user’s session. By changing the header, a tester signed in as an admin of one tenant listed the users, roles and email addresses of another tenant.
Impact
Any customer admin can read other customers’ user accounts and role assignments.
How to fix it
Derive the tenant from the authenticated session on the server, never from client input. Apply a tenant filter in the data layer for every query, and add automated tests that request another tenant’s objects.






