How to Fix Insecure Direct Object References (IDOR) in Django
Learn how to prevent and fix Insecure Direct Object References (IDOR) vulnerabilities in Django applications. Step-by-step guide with code examples, security checklists, and best practices.
What Is Insecure Direct Object References (IDOR)?
Insecure Direct Object References (IDOR) is an access control vulnerability where an application uses user-supplied input to directly access objects (like database records, files, or API resources) without verifying the user's authorization to access that specific object. The vulnerability occurs when internal identifiers such as database IDs, filenames, or sequential numbers are exposed in URLs, form fields, or API parameters.
For example, if a user can view their invoice at `/api/invoices/1234` and simply changing the ID to `/api/invoices/1235` reveals another user's invoice, that is an IDOR vulnerability. The application checked that the user was authenticated but failed to verify that the specific invoice belongs to that user.
IDOR is extremely common in modern web applications, particularly those with RESTful APIs where resource identifiers are part of the URL path. It is often introduced when developers focus on authentication (is the user logged in?) but neglect authorization (is this user allowed to access this specific resource?). Even applications using UUIDs instead of sequential integers can be vulnerable if the UUIDs are leaked or predictable.
Why It Matters
IDOR vulnerabilities can expose sensitive data belonging to other users, including personal information, financial records, private messages, and documents. Because IDOR exploits are simple (often just changing a number in a URL), they are frequently discovered by unsophisticated attackers or automated scanners. The impact scales with the sensitivity of the exposed data and the number of affected records. In multi-tenant SaaS applications, IDOR can allow one customer to access another customer's data, leading to severe trust and compliance issues. IDOR was a factor in several major data breaches, including the 2019 First American Financial breach that exposed 885 million records.
How to Fix It in Django
Implement proper authorization checks for every data access operation. Never rely solely on authentication -- verify that the authenticated user has permission to access the specific requested resource. In database queries, always filter by the current user's ID or organization (e.g., `WHERE user_id = :currentUser AND id = :requestedId`). Use Supabase Row Level Security (RLS) policies or similar database-level access controls. Replace sequential IDs with UUIDs in public-facing interfaces to reduce enumeration risk (but still verify authorization). Implement access control at the service layer, not just the controller layer. Conduct authorization testing as part of your security review process.
Django-Specific Advice
- Django's template engine auto-escapes HTML by default. Never use the `|safe` filter or `mark_safe()` with unsanitized user input.
- Use Django's ORM for all database queries. When raw SQL is needed, always use parameterized queries: `cursor.execute('SELECT ... WHERE id = %s', [user_id])`.
- Keep Django's CSRF middleware enabled. Use `{% csrf_token %}` in all forms and configure CSRF for AJAX requests.
- Set `DEBUG = False` in production. Debug mode exposes detailed error pages with sensitive information.
Django Security Checklist for Insecure Direct Object References (IDOR)
Django Security Best Practices
Django's template engine auto-escapes HTML by default. Never use the `|safe` filter or `mark_safe()` with unsanitized user input.
Use Django's ORM for all database queries. When raw SQL is needed, always use parameterized queries: `cursor.execute('SELECT ... WHERE id = %s', [user_id])`.
Keep Django's CSRF middleware enabled. Use `{% csrf_token %}` in all forms and configure CSRF for AJAX requests.
Set `DEBUG = False` in production. Debug mode exposes detailed error pages with sensitive information.
Use Django's built-in password hashing (PBKDF2 by default) and never implement custom password storage.
Configure `SECURE_SSL_REDIRECT`, `SECURE_HSTS_SECONDS`, `SESSION_COOKIE_SECURE`, and `CSRF_COOKIE_SECURE` in production settings.
Use `django-ratelimit` or Django REST Framework's throttling for rate limiting on authentication and API endpoints.
Keep `SECRET_KEY` secret and unique per environment. Rotate it if it is ever exposed.
Scan Your Django App with SafeVibe
Stop guessing if your Django app is vulnerable to Insecure Direct Object References (IDOR). Run an automated penetration test in minutes and get actionable results.
Start Free Scan