Common Issues
auth
Users Can See Each Other's Private Data
Users in your app can see data that belongs to other users — viewing other people's orders, messages, personal information, or account details. This is a serious privacy and security issue that needs to be fixed immediately.
Common Causes
- No Row Level Security (RLS) — database queries return all data, not just the current user's
- API endpoints don't filter data by the authenticated user's ID
- User ID taken from the request body instead of the authenticated session
- Shared cache serving one user's data to another
- Query fetches all records and filters on the frontend only
How to Fix It
- This is urgent — fix it before anything else. Consider taking the affected features offline temporarily.
- Check every API endpoint that returns user data — make sure it filters by the authenticated user's ID
- If using Supabase, implement RLS policies on all tables containing user data
- Never trust user ID from the request body — always get it from the server-side session
- Test by logging in as different users and verifying each only sees their own data
Real developers can help you.
Describe what's wrong in plain English. No technical knowledge needed.
Get HelpFrequently Asked Questions
How serious is this?
Very serious. This is a data privacy violation that could have legal consequences (GDPR, etc.). Fix it immediately and consider notifying affected users if sensitive data was exposed.
Can this be fixed without rebuilding the app?
Yes. Adding proper RLS policies (for Supabase) or API-level authorization checks can fix this without a rebuild. A developer can usually fix it within a day.