--- name: payloads-idor description: "Insecure Direct Object References (IDOR) is a security vulnerability that occurs when an application allows users to directly access or modify objects (such as files, database records, or URLs) based on user-supplied input, without sufficient access controls. This means that if a user changes a parameter value (like an ID) in a URL or API request, they might be able to access or manipulate data..." --- # IDOR Payloads > **Source:** [PayloadsAllTheThings/Insecure Direct Object References](https://github.com/swisskyrepo/payloadsallthethings/tree/master/Insecure%20Direct%20Object%20References) > **Category:** `payloads-web` | **Skill ID:** `payloads-idor` ## Overview IDOR/BOLA payloads for direct object reference attacks and authorization bypass techniques. This skill integrates the full **PayloadsAllTheThings** (PATT) payload library for the **IDOR Payloads** domain into the REA_Skill framework. Use it during authorized penetration testing, bug bounty research, security audits, and CTF challenges. ## Workflow ### 1. Recon & Identification - Identify the target technology stack and injection points - Enumerate endpoints, parameters, and input vectors - Determine applicable payload categories from the reference below ### 2. Payload Selection - Browse the PATT payload library for the attack class - Select encoding-appropriate payloads for the target environment - Consider WAF bypass variants and obfuscation techniques ### 3. Exploitation (Authorized Only) - Test payloads in order: passive → active → escalation - Document every payload tested and its response - Capture PoC evidence (screenshots, HTTP logs, curl output) ### 4. Verification & Reporting - Confirm the vulnerability with a clean minimal PoC - Map findings to CVE/CWE where applicable - Report with remediation recommendations and code fixes --- ## Full PATT Reference # Insecure Direct Object References > Insecure Direct Object References (IDOR) is a security vulnerability that occurs when an application allows users to directly access or modify objects (such as files, database records, or URLs) based on user-supplied input, without sufficient access controls. This means that if a user changes a parameter value (like an ID) in a URL or API request, they might be able to access or manipulate data that they aren’t authorized to see or modify. ## Summary * [Tools](#tools) * [Methodology](#methodology) * [Numeric Value Parameter](#numeric-value-parameter) * [Common Identifiers Parameter](#common-identifiers-parameter) * [Weak Pseudo Random Number Generator](#weak-pseudo-random-number-generator) * [Hashed Parameter](#hashed-parameter) * [Wildcard Parameter](#wildcard-parameter) * [IDOR Tips](#idor-tips) * [Labs](#labs) * [References](#references) ## Tools * [PortSwigger/BApp Store > Authz](https://portswigger.net/bappstore/4316cc18ac5f434884b2089831c7d19e) * [PortSwigger/BApp Store > AuthMatrix](https://portswigger.net/bappstore/30d8ee9f40c041b0bfec67441aad158e) * [PortSwigger/BApp Store > Autorize](https://portswigger.net/bappstore/f9bbac8c4acf4aefa4d7dc92a991af2f) ## Methodology IDOR stands for Insecure Direct Object Reference. It's a type of security vulnerability that arises when an application provides direct access to objects based on user-supplied input. As a result, attackers can bypass authorization and access resources in the system directly, potentially leading to unauthorized information disclosure, modification, or deletion. **Example of IDOR**: Imagine a web application that allows users to view their profile by clicking a link `https://example.com/profile?user_id=123`: ```php ⚠️ **Authorized Use Only.** All payloads in this skill are for security research, penetration testing with written permission, CTF competitions, and defensive study. Unauthorized use against systems you do not own or have explicit permission to test is illegal.