Insecure Direct Object Reference (IDOR)
A route through the library rather than a dump of it. Items are drawn from the full IDOR collection, filtered to teaching material (news items are excluded) and ordered within each stage by depth signals โ whether the piece carries code, how substantial it is, and what readers actually open.
1
Start here
5 resourcesOrientation and first principles โ what the bug class is and how it behaves.
- GraphQL IDOR Vulnerabilities: What They Are and How to FixLibrary focusing on preventing Insecure Direct Object References (IDOR) in GraphQL APIs. It details how IDOR vulnerabilities arise from improper validation of object identifiers, allowing unauthorized data access. The resource highlights real-world examples like vulnerabilities in PayPal, Vimeo, and Shopify, and provides practical advice on implementing strong authentication and strict authorization checks within GraphQL resolvers to mitigate these risks.
- IDOR Attack Guide | HackviserGuide detailing Insecure Direct Object Reference (IDOR) vulnerabilities, explaining how attackers exploit missing authorization checks in applications. It covers manual testing techniques including URL parameter, POST body, HTTP header, cookie, file access, and API endpoint manipulation. The guide also outlines automated discovery methods using Burp Suite and ffuf, and explores attack vectors like numeric and GUID/UUID manipulation, hash-based bypass, parameter pollution, mass assignment, and blind IDOR exploitation.
- IDOR Vulnerability Exploitation Guide โ RedfoxSecGuide to Insecure Direct Object Reference (IDOR) vulnerabilities, a critical OWASP Top 10 risk. This resource details how IDORs occur when applications trust user-provided object references without proper authorization checks, enabling unauthorized access to sensitive data. It covers common exploitation techniques like incrementing integer IDs, predictable GUIDs, and path traversal with examples using tools like Burp Suite Intruder and `curl`. The guide also discusses horizontal and vertical IDOR, provides a methodology for discovery, and highlights the importance of testing PUT, DELETE, and PATCH requests, along with harvesting object references from API responses.
- What is IDOR? Complete GuideGuide to Insecure Direct Object References (IDOR), this document details how broken access control vulnerabilities allow attackers to manipulate direct object references like database keys or query parameters to access unauthorized data. It covers how IDORs work, including URL tampering, body manipulation, and cookie/JSON manipulation, and explains the risks such as data confidentiality breaches and integrity corruption. The guide also discusses detection methods using tools like Burp Suite and OWASP ZAP, and prevention techniques involving robust access control and session management.
- IDOR, The Beginnerโs Goldmine: The Bug Bounty Field ManualLibrary for teaching Insecure Direct Object Reference (IDOR) vulnerabilities, a key bug class for beginners in bug bounty hunting. It details IDOR patterns like sequential IDs, GraphQL node substitution, session object misbinding, cross-tenant boundary failures, and error response leakage, using examples from GitLab and HackerOne. The resource guides users through testing IDOR with two accounts and a proxy like Burp Suite, emphasizing the importance of authorization checks and clear reporting.
2
Build depth
5 resourcesReal testing methodology, tooling, and writeups that show the work.
- How I Found a Cross-Student IDOR in Academy LMS That Leaked Correct Quiz AnswersWriteup of a Cross-Student IDOR vulnerability in Academy LMS plugin, affecting over 2,000 installations. The vulnerability, discovered by analyzing the plugin's API controllers, allowed any enrolled student to view another student's quiz results and obtain correct answers. This was achieved by exploiting two authorization failures in the `get_student_quiz_attempt_details` endpoint, which incorrectly processed the `user_id` parameter from requests and evaluated access permissions against the target user's context rather than the caller's.
- Critical Bookly IDOR: booking disclosure and deletionLibrary for identifying and exploiting CVE-2026-93399, an unauthenticated Insecure Direct Object Reference (IDOR) in the Bookly WordPress appointment booking plugin. This vulnerability allows attackers to disclose customer bookings, including Personally Identifiable Information (PII), and to delete bookings by chaining an attacker-controlled order ID through the `bookly_get_form_id` and `bookly_render_complete` AJAX actions to obtain a `bookly_order` token, which can then be used with `bookly_add_to_calendar` for disclosure or `bookly_rollback_order` for deletion. Affected versions are Bookly up to and including 28.2.
- ExploitSpec โ BOLA/IDOR regression tests from bounded, redacted HAR inputLibrary for creating regression tests from existing HTTP exploits, specifically designed for BOLA/IDOR vulnerabilities. ExploitSpec allows security invariants to be kept alongside application code, enabling local and CI-based re-runs. It supports isolating actor headers, cookies, and sessions, capturing dynamic values for later use, and emitting results in readable text, JSON, or JUnit formats. The tool helps ensure that confirmed vulnerabilities do not reappear by proving RED, GREEN, and STABLE states before build failure.
- GraphQL BOLA: one object, many paths, and how to prove the gapLibrary for identifying and exploiting GraphQL BOLA vulnerabilities by demonstrating how to map all potential object access paths. It guides users through schema introspection, utilizing tools like Clairvoyance or frontend analysis to uncover all resolvers that can return a specific type, including those mediated by interfaces like `Node`. The library advocates for testing each discovered path with distinct user accounts in a single request, leveraging GraphQL aliases to pinpoint authorization gaps where one resolver correctly checks ownership while others fail to do so, a common issue highlighted in the OWASP API Security Top 10 2023.
- Cross-project form-session IDOR in CommCare formplayer (GHSA-qjg7-cgv8-3c43)Library for validating user ownership of form sessions in CommCare's formplayer application. This vulnerability (GHSA-qjg7-cgv8-3c43) allowed users to access, alter, or delete incomplete forms belonging to other users in different project spaces. The fix involved adding a `@ValidateSessionOwner` annotation to routes that resolve sessions by ID, ensuring the caller's identity is checked against the session's owner. This addresses CWE-639 and CWE-862.
3
Go deep
5 resourcesNovel research, edge cases, and the techniques that push the class forward.
- Insecure Direct Object Reference (IDOR) - A Deep DiveLibrary covering Insecure Direct Object Reference (IDOR) vulnerabilities, detailing exploitation techniques such as ID parameter manipulation, direct request, mass assignment, token prediction, file path traversal, and API endpoint enumeration. It provides code examples for vulnerable and remediated scenarios, highlighting the impact of IDORs and mentioning CVE-2023-4836 in the User Private Files plugin for WordPress. Remediation strategies include implementing proper access control, using indirect references, employing GUIDs, and validating user input.
- Predicting MongoDB ObjectId() continuously in Rocket.ChatWriteup detailing a vulnerability in Rocket.Chat, #3687142, where unauthenticated users can access any uploaded file by predicting its MongoDB ObjectId(). The article explains how the ObjectId() is composed of a timestamp, machine/process ID, and a counter, allowing attackers to enumerate valid file IDs and bypass authorization checks through the Livechat functionality.
- New Types of Hacking: IDOR Attacks EvolvedNew Types of Hacking: IDOR Attacks Evolved
- Broken Access Control: Advanced IDOR ExploitationLibrary for advanced exploitation of broken access control vulnerabilities, focusing on Insecure Direct Object References (IDORs). It covers "object-based" IDORs with JSON manipulation, multi-step IDORs hidden behind workflow sequences, second-order IDORs where input indirectly references resources, and "ID-less" IDORs that bypass direct ID references. Techniques explored include wrapping IDs in arrays, object mapping, boolean usage, and various ID manipulation attempts.
- Chaining password reset link poisoning IDOR and information leakage to achieve account takeover at api.redacted.comA security researcher successfully exploited a vulnerability at api.redacted.com, achieving account takeover. The attack involved chaining together three distinct vulnerabilities: password reset link poisoning, an Insecure Direct Object Reference (IDOR), and information leakage. This combination allowed the attacker to gain unauthorized access to user accounts.