Authorization

IDOR Scanner

Detect routes where object IDs can be changed and understand whether cross-user access was actually proven.

Fixnx report
Live scan
ID-based URLshigh
Object mutationhigh
Session-aware probeschecked
Ownership markerschecked
UserA/UserB proofchecked

What this page helps you understand

IDOR testing needs more than a 200 response. Fixnx reports ID mutation as likely unless separate user contexts prove that one user accessed another user's object.

What Fixnx checks

ID-based URLs

Object mutation

Session-aware probes

Ownership markers

UserA/UserB proof

Response comparison

A real IDOR finding needs ownership proof

Changing an ID and receiving 200 is a signal, not proof. The response might be public, empty, or scoped correctly.

Fixnx keeps that distinction visible. Confirmed IDOR requires evidence that one user accessed data owned by another user.

For best results, provide userA and userB sessions so the scanner can compare ownership boundaries.

Run this check on your site

Enter a public URL and get a live Fixnx report with security, SEO, and performance checks.

Scan now. Google sign-in is only needed to unlock fix guidance.

FAQ

Why was my IDOR finding likely instead of confirmed?

Because the scan observed successful ID mutation but did not prove cross-user ownership exposure.

How do I confirm IDOR?

Provide two separate authenticated user contexts so the scanner can test user-owned resources across accounts.