Block an IDOR vulnerability by checking who owns each record
An IDOR vulnerability lets someone reach another person's data by changing an identifier. Being signed in doesn't give a user permission to access every record.
npm install --save-dev @sitecmd/cli
npx sitecmd audit .
The CLI runs on your computer or in your CI, and your code stays there.
What it finds on a demo project
The audit points to account, billing, admin and workspace handlers that reach data with no ownership, role or tenant check, and to apps whose sign-in checks run only in the browser.
SiteCMD CLI 2.0.0
Demo project: Billing and admin API
npx sitecmd audit .
SiteCMD Code Scan - .
Checked: November 9, 2026
Framework: Express
Issues: 5 total | critical 0 | high 3 | medium 2 | low 0
High (3)
- [Security · security] No recognized local auth gate for a sensitive-looking handler - src/routes/admin.js:9
- [Security · security] No recognized local authorization decision for a sensitive handler - src/routes/billing.js:6
- [Security · security] No recognized tenant or owner scope in authenticated handler - src/routes/billing.js:8
Medium (2)
- [Architecture · architecture] Route handler contains direct database access - src/routes/admin.js:3
- [Architecture · architecture] Route handler contains direct database access - src/routes/billing.js:2
Your code passes? Now watch your site.
Prevent insecure direct object references on reads and writes
Look up the requested record within the data the signed-in user may access. Check that permission whenever the app reads or changes the object. OWASP's IDOR guidance explains why a record ID alone isn't enough.
Scope multi-tenant data isolation to the signed-in tenant
Get the active tenant and membership from a verified server session. Use that to limit database reads and writes, rather than trusting a tenant ID sent by the browser.
Enforce tenant isolation beyond the sign-in screen
Hiding a button or redirecting the browser doesn't enforce a permission on the server.
Frequently asked questions
Do UUIDs prevent an IDOR vulnerability?
No. Harder-to-guess IDs can reduce guessing, but every object still needs an access check. A user who gets someone else's ID must still be refused.
Follow the identity behind each access decision
Website security
Catch leaked API keys and exposed files before someone uses them against you.
Supabase RLS
Check that each table's policies keep users to their own rows.
How to store passwords
Store a slow, salted hash instead of the password itself.