Fix · Sign-in and accounts

A logged-in user can see another user's data

UrgentSecurity

What you may see

Changing the number in the address shows someone else's order or profile
A customer saw another customer's details

Most likely cause

The server finds a record by its number without checking that it belongs to the person asking.

Check first (about two minutes)

The fix prompt

What you type here never leaves your browser. The search runs on this page, and nothing is sent to a server or to an AI.

The exact error or what you see

What you did before it happened

Kept only in this browser, on this device. Keys and passwords are removed before anything is saved.

Prompt language

You are a careful senior engineer who knows sign-in, sessions and user accounts, and explains them to people who are not developers. I am not a developer, so explain every step in plain words and tell me exactly which button, menu or command you mean. If you are not sure about something, say so; do not guess.

This is urgent. Do the safety steps first, before anything else.

THE PROBLEM
A logged-in user can see another user's data

THE EXACT ERROR OR WHAT I SEE
[paste the exact error here]

WHAT I DID BEFORE IT HAPPENED
[write in a few words what you did before it happened]

MOST LIKELY CAUSE
The server finds a record by its number without checking that it belongs to the person asking.

DO THESE STEPS, IN THIS ORDER
1. List every page, API route and action that takes an id (orders, profiles, files, invoices).
2. For each, make the SERVER check that the record belongs to the signed-in user (or the user has a staff role), and reply "not found" otherwise; add database rules (row level security) as a second wall.
3. Use long random ids for anything shown in addresses (not 1, 2, 3).
4. Add tests with two test users that try to read, change and delete each other's records.
Stop and tell me if what you see does not match a step. Do not skip ahead.

CHECK THAT IT WORKED
- Test user A gets "not found" for every record of test user B, on pages, API calls and files.
Tell me exactly what I should see on the screen when it works.

DO NOT CHANGE
- Do not test with real customers' data.
- Anything I did not ask about: the design, the text, other pages, other settings or the data.
- Do not delete files, data or branches, do not reset or force-push, and do not rewrite history, unless you first show me exactly what would be lost and I say yes.
- Do not paste, print or ask me to paste a password or secret key into this chat. If one is needed, tell me which settings page of the right service to store it in.

WHEN YOU FINISH
Explain in simple words what you changed (file by file or setting by setting), why you changed it, and how I can undo it.

Paste it into Claude, ChatGPT, Gemini or Cursor, then follow what it says.

After you tried it, did it work?

Steps

List every page, API route and action that takes an id (orders, profiles, files, invoices).
For each, make the SERVER check that the record belongs to the signed-in user (or the user has a staff role), and reply "not found" otherwise; add database rules (row level security) as a second wall.
Use long random ids for anything shown in addresses (not 1, 2, 3).
Add tests with two test users that try to read, change and delete each other's records.

Do not do this

Do not rely on hiding links.
Do not test with real customers' data.

Try another entry