[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AFST42FFV9HBHWT25R0NRR":3,"skill-same:01M6AFST42FFV9HBHWT25R0NRR":85},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":29,"publishedAt":53,"linkOnly":54,"markdownContent":55,"markdownBody":56,"frontMatter":57,"refName":61,"commitSha":62,"skillDirectory":63,"forksCount":64,"repositoryHtmlUrl":65,"repositoryHomepageUrl":66,"ownerHtmlUrl":67,"ownerBlogUrl":68,"ownerDescription":69,"updatedAt":70,"install":71,"resources":84},"01M6AFST42FFV9HBHWT25R0NRR","idor-testing",null,"This skill should be used when the user asks to \"test for insecure direct object references,\" \"find IDOR vulnerabilities,\" \"exploit broken access control,\" \"enumerate user IDs or object references,\" or \"bypass authorization to access other users' data.\" It provides comprehensive guidance for detecting, exploiting, and remediating IDOR vulnerabilities in web applications.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33418,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fidor-testing\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52],"idor","idor testing","testing","direct","when","for","object","detecting","users","Access Control","references","guidance","exploit","user","broken","access","applications","ids","authorization","data","web","test","vulnerabilities","2026-11-10 10:12:30",false,"---\nname: idor-testing\ndescription: This skill should be used when the user asks to \"test for insecure direct object references,\" \"find IDOR vulnerabilities,\" \"exploit broken access control,\" \"enumerate user IDs or object references,\" or \"bypass authorization to access other users' data.\" It provides comprehensive guidance for detecting, exploiting, and remediating IDOR vulnerabilities in web applications.\nmetadata:\n  author: zebbern\n  version: \"1.1\"\n---\n\n# IDOR Vulnerability Testing\n\n## Purpose\n\nProvide systematic methodologies for identifying and exploiting Insecure Direct Object Reference (IDOR) vulnerabilities in web applications. This skill covers both database object references and static file references, detection techniques using parameter manipulation and enumeration, exploitation via Burp Suite, and remediation strategies for securing applications against unauthorized access.\n\n## Inputs \u002F Prerequisites\n\n- **Target Web Application**: URL of application with user-specific resources\n- **Multiple User Accounts**: At least two test accounts to verify cross-user access\n- **Burp Suite or Proxy Tool**: Intercepting proxy for request manipulation\n- **Authorization**: Written permission for security testing\n- **Understanding of Application Flow**: Knowledge of how objects are referenced (IDs, filenames)\n\n## Outputs \u002F Deliverables\n\n- **IDOR Vulnerability Report**: Documentation of discovered access control bypasses\n- **Proof of Concept**: Evidence of unauthorized data access across user contexts\n- **Affected Endpoints**: List of vulnerable API endpoints and parameters\n- **Impact Assessment**: Classification of data exposure severity\n- **Remediation Recommendations**: Specific fixes for identified vulnerabilities\n\n## Core Workflow\n\n### 1. Understand IDOR Vulnerability Types\n\n#### Direct Reference to Database Objects\nOccurs when applications reference database records via user-controllable parameters:\n```\n# Original URL (authenticated as User A)\nexample.com\u002Fuser\u002Fprofile?id=2023\n\n# Manipulation attempt (accessing User B's data)\nexample.com\u002Fuser\u002Fprofile?id=2022\n```\n\n#### Direct Reference to Static Files\nOccurs when applications expose file paths or names that can be enumerated:\n```\n# Original URL (User A's receipt)\nexample.com\u002Fstatic\u002Freceipt\u002F205.pdf\n\n# Manipulation attempt (User B's receipt)\nexample.com\u002Fstatic\u002Freceipt\u002F200.pdf\n```\n\n### 2. Reconnaissance and Setup\n\n#### Create Multiple Test Accounts\n```\nAccount 1: \"attacker\" - Primary testing account\nAccount 2: \"victim\" - Account whose data we attempt to access\n```\n\n#### Identify Object References\nCapture and analyze requests containing:\n- Numeric IDs in URLs: `\u002Fapi\u002Fuser\u002F123`\n- Numeric IDs in parameters: `?id=123&action=view`\n- Numeric IDs in request body: `{\"userId\": 123}`\n- File paths: `\u002Fdownload\u002Freceipt_123.pdf`\n- GUIDs\u002FUUIDs: `\u002Fprofile\u002Fa1b2c3d4-e5f6-...`\n\n#### Map User IDs\n```\n# Access user ID endpoint (if available)\nGET \u002Fapi\u002Fuser-id\u002F\n\n# Note ID patterns:\n# - Sequential integers (1, 2, 3...)\n# - Auto-incremented values\n# - Predictable patterns\n```\n\n### 3. Detection Techniques\n\n#### URL Parameter Manipulation\n```\n# Step 1: Capture original authenticated request\nGET \u002Fapi\u002Fuser\u002Fprofile?id=1001 HTTP\u002F1.1\nCookie: session=attacker_session\n\n# Step 2: Modify ID to target another user\nGET \u002Fapi\u002Fuser\u002Fprofile?id=1000 HTTP\u002F1.1\nCookie: session=attacker_session\n\n# Vulnerable if: Returns victim's data with attacker's session\n```\n\n#### Request Body Manipulation\n```\n# Original POST request\nPOST \u002Fapi\u002Faddress\u002Fupdate HTTP\u002F1.1\nContent-Type: application\u002Fjson\nCookie: session=attacker_session\n\n{\"id\": 5, \"userId\": 1001, \"address\": \"123 Attacker St\"}\n\n# Modified request targeting victim\n{\"id\": 5, \"userId\": 1000, \"address\": \"123 Attacker St\"}\n```\n\n#### HTTP Method Switching\n```\n# Original GET request may be protected\nGET \u002Fapi\u002Fadmin\u002Fusers\u002F1000 → 403 Forbidden\n\n# Try alternative methods\nPOST \u002Fapi\u002Fadmin\u002Fusers\u002F1000 → 200 OK (Vulnerable!)\nPUT \u002Fapi\u002Fadmin\u002Fusers\u002F1000 → 200 OK (Vulnerable!)\n```\n\n### 4. Exploitation with Burp Suite\n\n#### Manual Exploitation\n```\n1. Configure browser proxy through Burp Suite\n2. Login as \"attacker\" user\n3. Navigate to profile\u002Fdata page\n4. Enable Intercept in Proxy tab\n5. Capture request with user ID\n6. Modify ID to victim's ID\n7. Forward request\n8. Observe response for victim's data\n```\n\n#### Automated Enumeration with Intruder\n```\n1. Send request to Intruder (Ctrl+I)\n2. Clear all payload positions\n3. Select ID parameter as payload position\n4. Configure attack type: Sniper\n5. Payload settings:\n   - Type: Numbers\n   - Range: 1 to 10000\n   - Step: 1\n6. Start attack\n7. Analyze responses for 200 status codes\n```\n\n#### Battering Ram Attack for Multiple Positions\n```\n# When same ID appears in multiple locations\nPUT \u002Fapi\u002Faddresses\u002F§5§\u002Fupdate HTTP\u002F1.1\n\n{\"id\": §5§, \"userId\": 3}\n\nAttack Type: Battering Ram\nPayload: Numbers 1-1000\n```\n\n### 5. Common IDOR Locations\n\n#### API Endpoints\n```\n\u002Fapi\u002Fuser\u002F{id}\n\u002Fapi\u002Fprofile\u002F{id}\n\u002Fapi\u002Forder\u002F{id}\n\u002Fapi\u002Finvoice\u002F{id}\n\u002Fapi\u002Fdocument\u002F{id}\n\u002Fapi\u002Fmessage\u002F{id}\n\u002Fapi\u002Faddress\u002F{id}\u002Fupdate\n\u002Fapi\u002Faddress\u002F{id}\u002Fdelete\n```\n\n#### File Downloads\n```\n\u002Fdownload\u002Finvoice_{id}.pdf\n\u002Fstatic\u002Freceipts\u002F{id}.pdf\n\u002Fuploads\u002Fdocuments\u002F{filename}\n\u002Ffiles\u002Freports\u002Freport_{date}_{id}.xlsx\n```\n\n#### Query Parameters\n```\n?userId=123\n?orderId=456\n?documentId=789\n?file=report_123.pdf\n?account=user@email.com\n```\n\n## Quick Reference\n\n### IDOR Testing Checklist\n\n| Test | Method | Indicator of Vulnerability |\n|------|--------|---------------------------|\n| Increment\u002FDecrement ID | Change `id=5` to `id=4` | Returns different user's data |\n| Use Victim's ID | Replace with known victim ID | Access granted to victim's resources |\n| Enumerate Range | Test IDs 1-1000 | Find valid records of other users |\n| Negative Values | Test `id=-1` or `id=0` | Unexpected data or errors |\n| Large Values | Test `id=99999999` | System information disclosure |\n| String IDs | Change format `id=user_123` | Logic bypass |\n| GUID Manipulation | Modify UUID portions | Predictable UUID patterns |\n\n### Response Analysis\n\n| Status Code | Interpretation |\n|-------------|----------------|\n| 200 OK | Potential IDOR - verify data ownership |\n| 403 Forbidden | Access control working |\n| 404 Not Found | Resource doesn't exist |\n| 401 Unauthorized | Authentication required |\n| 500 Error | Potential input validation issue |\n\n### Common Vulnerable Parameters\n\n| Parameter Type | Examples |\n|----------------|----------|\n| User identifiers | `userId`, `uid`, `user_id`, `account` |\n| Resource identifiers | `id`, `pid`, `docId`, `fileId` |\n| Order\u002FTransaction | `orderId`, `transactionId`, `invoiceId` |\n| Message\u002FCommunication | `messageId`, `threadId`, `chatId` |\n| File references | `filename`, `file`, `document`, `path` |\n\n## Constraints and Limitations\n\n### Operational Boundaries\n- Requires at least two valid user accounts for verification\n- Some applications use session-bound tokens instead of IDs\n- GUID\u002FUUID references harder to enumerate but not impossible\n- Rate limiting may restrict enumeration attempts\n- Some IDOR requires chained vulnerabilities to exploit\n\n### Detection Challenges\n- Horizontal privilege escalation (user-to-user) vs vertical (user-to-admin)\n- Blind IDOR where response doesn't confirm access\n- Time-based IDOR in asynchronous operations\n- IDOR in websocket communications\n\n### Legal Requirements\n- Only test applications with explicit authorization\n- Document all testing activities and findings\n- Do not access, modify, or exfiltrate real user data\n- Report findings through proper disclosure channels\n\n## Examples\n\n### Example 1: Basic ID Parameter IDOR\n```\n# Login as attacker (userId=1001)\n# Navigate to profile page\n\n# Original request\nGET \u002Fapi\u002Fprofile?id=1001 HTTP\u002F1.1\nCookie: session=abc123\n\n# Response: Attacker's profile data\n\n# Modified request (targeting victim userId=1000)\nGET \u002Fapi\u002Fprofile?id=1000 HTTP\u002F1.1\nCookie: session=abc123\n\n# Vulnerable Response: Victim's profile data returned!\n```\n\n### Example 2: IDOR in Address Update Endpoint\n```\n# Intercept address update request\nPUT \u002Fapi\u002Faddresses\u002F5\u002Fupdate HTTP\u002F1.1\nContent-Type: application\u002Fjson\nCookie: session=attacker_session\n\n{\n  \"id\": 5,\n  \"userId\": 1001,\n  \"street\": \"123 Main St\",\n  \"city\": \"Test City\"\n}\n\n# Modify userId to victim's ID\n{\n  \"id\": 5,\n  \"userId\": 1000,  # Changed from 1001\n  \"street\": \"Hacked Address\",\n  \"city\": \"Exploit City\"\n}\n\n# If 200 OK: Address created under victim's account\n```\n\n### Example 3: Static File IDOR\n```\n# Download own receipt\nGET \u002Fapi\u002Fdownload\u002F5 HTTP\u002F1.1\nCookie: session=attacker_session\n\n# Response: PDF of attacker's receipt (order #5)\n\n# Attempt to access other receipts\nGET \u002Fapi\u002Fdownload\u002F3 HTTP\u002F1.1\nCookie: session=attacker_session\n\n# Vulnerable Response: PDF of victim's receipt (order #3)!\n```\n\n### Example 4: Burp Intruder Enumeration\n```\n# Configure Intruder attack\nTarget: PUT \u002Fapi\u002Faddresses\u002F§1§\u002Fupdate\nPayload Position: Address ID in URL and body\n\nAttack Configuration:\n- Type: Battering Ram\n- Payload: Numbers 0-20, Step 1\n\nBody Template:\n{\n  \"id\": §1§,\n  \"userId\": 3\n}\n\n# Analyze results:\n# - 200 responses indicate successful modification\n# - Check victim's account for new addresses\n```\n\n### Example 5: Horizontal to Vertical Escalation\n```\n# Step 1: Enumerate user roles\nGET \u002Fapi\u002Fuser\u002F1 → {\"role\": \"user\", \"id\": 1}\nGET \u002Fapi\u002Fuser\u002F2 → {\"role\": \"user\", \"id\": 2}\nGET \u002Fapi\u002Fuser\u002F3 → {\"role\": \"admin\", \"id\": 3}\n\n# Step 2: Access admin functions with discovered ID\nGET \u002Fapi\u002Fadmin\u002Fdashboard?userId=3 HTTP\u002F1.1\nCookie: session=regular_user_session\n\n# If accessible: Vertical privilege escalation achieved\n```\n\n## Troubleshooting\n\n### Issue: All Requests Return 403 Forbidden\n**Cause**: Server-side access control is implemented\n**Solution**:\n```\n# Try alternative attack vectors:\n1. HTTP method switching (GET → POST → PUT)\n2. Add X-Original-URL or X-Rewrite-URL headers\n3. Try parameter pollution: ?id=1001&id=1000\n4. URL encoding variations: %31%30%30%30 for \"1000\"\n5. Case variations for string IDs\n```\n\n### Issue: Application Uses UUIDs Instead of Sequential IDs\n**Cause**: Randomized identifiers reduce enumeration risk\n**Solution**:\n```\n# UUID discovery techniques:\n1. Check response bodies for leaked UUIDs\n2. Search JavaScript files for hardcoded UUIDs\n3. Check API responses that list multiple objects\n4. Look for UUID patterns in error messages\n5. Try UUID v1 (time-based) prediction if applicable\n```\n\n### Issue: Session Token Bound to User\n**Cause**: Application validates session against requested resource\n**Solution**:\n```\n# Advanced bypass attempts:\n1. Test for IDOR in unauthenticated endpoints\n2. Check password reset\u002Femail verification flows\n3. Look for IDOR in file upload\u002Fdownload\n4. Test API versioning: \u002Fapi\u002Fv1\u002F vs \u002Fapi\u002Fv2\u002F\n5. Check mobile API endpoints (often less protected)\n```\n\n### Issue: Rate Limiting Blocks Enumeration\n**Cause**: Application implements request throttling\n**Solution**:\n```\n# Bypass techniques:\n1. Add delays between requests (Burp Intruder throttle)\n2. Rotate IP addresses (proxy chains)\n3. Target specific high-value IDs instead of full range\n4. Use different endpoints for same resources\n5. Test during off-peak hours\n```\n\n### Issue: Cannot Verify IDOR Impact\n**Cause**: Response doesn't clearly indicate data ownership\n**Solution**:\n```\n# Verification methods:\n1. Create unique identifiable data in victim account\n2. Look for PII markers (name, email) in responses\n3. Compare response lengths between users\n4. Check for timing differences in responses\n5. Use secondary indicators (creation dates, metadata)\n```\n\n## Remediation Guidance\n\n### Implement Proper Access Control\n```python\n# Django example - validate ownership\ndef update_address(request, address_id):\n    address = Address.objects.get(id=address_id)\n    \n    # Verify ownership before allowing update\n    if address.user != request.user:\n        return HttpResponseForbidden(\"Unauthorized\")\n    \n    # Proceed with update\n    address.update(request.data)\n```\n\n### Use Indirect References\n```python\n# Instead of: \u002Fapi\u002Faddress\u002F123\n# Use: \u002Fapi\u002Faddress\u002Fcurrent-user\u002Fbilling\n\ndef get_address(request):\n    # Always filter by authenticated user\n    address = Address.objects.filter(user=request.user).first()\n    return address\n```\n\n### Server-Side Validation\n```python\n# Always validate on server, never trust client input\ndef download_receipt(request, receipt_id):\n    receipt = Receipt.objects.filter(\n        id=receipt_id,\n        user=request.user  # Critical: filter by current user\n    ).first()\n    \n    if not receipt:\n        return HttpResponseNotFound()\n    \n    return FileResponse(receipt.file)\n```\n","# IDOR Vulnerability Testing\n\n## Purpose\n\nProvide systematic methodologies for identifying and exploiting Insecure Direct Object Reference (IDOR) vulnerabilities in web applications. This skill covers both database object references and static file references, detection techniques using parameter manipulation and enumeration, exploitation via Burp Suite, and remediation strategies for securing applications against unauthorized access.\n\n## Inputs \u002F Prerequisites\n\n- **Target Web Application**: URL of application with user-specific resources\n- **Multiple User Accounts**: At least two test accounts to verify cross-user access\n- **Burp Suite or Proxy Tool**: Intercepting proxy for request manipulation\n- **Authorization**: Written permission for security testing\n- **Understanding of Application Flow**: Knowledge of how objects are referenced (IDs, filenames)\n\n## Outputs \u002F Deliverables\n\n- **IDOR Vulnerability Report**: Documentation of discovered access control bypasses\n- **Proof of Concept**: Evidence of unauthorized data access across user contexts\n- **Affected Endpoints**: List of vulnerable API endpoints and parameters\n- **Impact Assessment**: Classification of data exposure severity\n- **Remediation Recommendations**: Specific fixes for identified vulnerabilities\n\n## Core Workflow\n\n### 1. Understand IDOR Vulnerability Types\n\n#### Direct Reference to Database Objects\nOccurs when applications reference database records via user-controllable parameters:\n```\n# Original URL (authenticated as User A)\nexample.com\u002Fuser\u002Fprofile?id=2023\n\n# Manipulation attempt (accessing User B's data)\nexample.com\u002Fuser\u002Fprofile?id=2022\n```\n\n#### Direct Reference to Static Files\nOccurs when applications expose file paths or names that can be enumerated:\n```\n# Original URL (User A's receipt)\nexample.com\u002Fstatic\u002Freceipt\u002F205.pdf\n\n# Manipulation attempt (User B's receipt)\nexample.com\u002Fstatic\u002Freceipt\u002F200.pdf\n```\n\n### 2. Reconnaissance and Setup\n\n#### Create Multiple Test Accounts\n```\nAccount 1: \"attacker\" - Primary testing account\nAccount 2: \"victim\" - Account whose data we attempt to access\n```\n\n#### Identify Object References\nCapture and analyze requests containing:\n- Numeric IDs in URLs: `\u002Fapi\u002Fuser\u002F123`\n- Numeric IDs in parameters: `?id=123&action=view`\n- Numeric IDs in request body: `{\"userId\": 123}`\n- File paths: `\u002Fdownload\u002Freceipt_123.pdf`\n- GUIDs\u002FUUIDs: `\u002Fprofile\u002Fa1b2c3d4-e5f6-...`\n\n#### Map User IDs\n```\n# Access user ID endpoint (if available)\nGET \u002Fapi\u002Fuser-id\u002F\n\n# Note ID patterns:\n# - Sequential integers (1, 2, 3...)\n# - Auto-incremented values\n# - Predictable patterns\n```\n\n### 3. Detection Techniques\n\n#### URL Parameter Manipulation\n```\n# Step 1: Capture original authenticated request\nGET \u002Fapi\u002Fuser\u002Fprofile?id=1001 HTTP\u002F1.1\nCookie: session=attacker_session\n\n# Step 2: Modify ID to target another user\nGET \u002Fapi\u002Fuser\u002Fprofile?id=1000 HTTP\u002F1.1\nCookie: session=attacker_session\n\n# Vulnerable if: Returns victim's data with attacker's session\n```\n\n#### Request Body Manipulation\n```\n# Original POST request\nPOST \u002Fapi\u002Faddress\u002Fupdate HTTP\u002F1.1\nContent-Type: application\u002Fjson\nCookie: session=attacker_session\n\n{\"id\": 5, \"userId\": 1001, \"address\": \"123 Attacker St\"}\n\n# Modified request targeting victim\n{\"id\": 5, \"userId\": 1000, \"address\": \"123 Attacker St\"}\n```\n\n#### HTTP Method Switching\n```\n# Original GET request may be protected\nGET \u002Fapi\u002Fadmin\u002Fusers\u002F1000 → 403 Forbidden\n\n# Try alternative methods\nPOST \u002Fapi\u002Fadmin\u002Fusers\u002F1000 → 200 OK (Vulnerable!)\nPUT \u002Fapi\u002Fadmin\u002Fusers\u002F1000 → 200 OK (Vulnerable!)\n```\n\n### 4. Exploitation with Burp Suite\n\n#### Manual Exploitation\n```\n1. Configure browser proxy through Burp Suite\n2. Login as \"attacker\" user\n3. Navigate to profile\u002Fdata page\n4. Enable Intercept in Proxy tab\n5. Capture request with user ID\n6. Modify ID to victim's ID\n7. Forward request\n8. Observe response for victim's data\n```\n\n#### Automated Enumeration with Intruder\n```\n1. Send request to Intruder (Ctrl+I)\n2. Clear all payload positions\n3. Select ID parameter as payload position\n4. Configure attack type: Sniper\n5. Payload settings:\n   - Type: Numbers\n   - Range: 1 to 10000\n   - Step: 1\n6. Start attack\n7. Analyze responses for 200 status codes\n```\n\n#### Battering Ram Attack for Multiple Positions\n```\n# When same ID appears in multiple locations\nPUT \u002Fapi\u002Faddresses\u002F§5§\u002Fupdate HTTP\u002F1.1\n\n{\"id\": §5§, \"userId\": 3}\n\nAttack Type: Battering Ram\nPayload: Numbers 1-1000\n```\n\n### 5. Common IDOR Locations\n\n#### API Endpoints\n```\n\u002Fapi\u002Fuser\u002F{id}\n\u002Fapi\u002Fprofile\u002F{id}\n\u002Fapi\u002Forder\u002F{id}\n\u002Fapi\u002Finvoice\u002F{id}\n\u002Fapi\u002Fdocument\u002F{id}\n\u002Fapi\u002Fmessage\u002F{id}\n\u002Fapi\u002Faddress\u002F{id}\u002Fupdate\n\u002Fapi\u002Faddress\u002F{id}\u002Fdelete\n```\n\n#### File Downloads\n```\n\u002Fdownload\u002Finvoice_{id}.pdf\n\u002Fstatic\u002Freceipts\u002F{id}.pdf\n\u002Fuploads\u002Fdocuments\u002F{filename}\n\u002Ffiles\u002Freports\u002Freport_{date}_{id}.xlsx\n```\n\n#### Query Parameters\n```\n?userId=123\n?orderId=456\n?documentId=789\n?file=report_123.pdf\n?account=user@email.com\n```\n\n## Quick Reference\n\n### IDOR Testing Checklist\n\n| Test | Method | Indicator of Vulnerability |\n|------|--------|---------------------------|\n| Increment\u002FDecrement ID | Change `id=5` to `id=4` | Returns different user's data |\n| Use Victim's ID | Replace with known victim ID | Access granted to victim's resources |\n| Enumerate Range | Test IDs 1-1000 | Find valid records of other users |\n| Negative Values | Test `id=-1` or `id=0` | Unexpected data or errors |\n| Large Values | Test `id=99999999` | System information disclosure |\n| String IDs | Change format `id=user_123` | Logic bypass |\n| GUID Manipulation | Modify UUID portions | Predictable UUID patterns |\n\n### Response Analysis\n\n| Status Code | Interpretation |\n|-------------|----------------|\n| 200 OK | Potential IDOR - verify data ownership |\n| 403 Forbidden | Access control working |\n| 404 Not Found | Resource doesn't exist |\n| 401 Unauthorized | Authentication required |\n| 500 Error | Potential input validation issue |\n\n### Common Vulnerable Parameters\n\n| Parameter Type | Examples |\n|----------------|----------|\n| User identifiers | `userId`, `uid`, `user_id`, `account` |\n| Resource identifiers | `id`, `pid`, `docId`, `fileId` |\n| Order\u002FTransaction | `orderId`, `transactionId`, `invoiceId` |\n| Message\u002FCommunication | `messageId`, `threadId`, `chatId` |\n| File references | `filename`, `file`, `document`, `path` |\n\n## Constraints and Limitations\n\n### Operational Boundaries\n- Requires at least two valid user accounts for verification\n- Some applications use session-bound tokens instead of IDs\n- GUID\u002FUUID references harder to enumerate but not impossible\n- Rate limiting may restrict enumeration attempts\n- Some IDOR requires chained vulnerabilities to exploit\n\n### Detection Challenges\n- Horizontal privilege escalation (user-to-user) vs vertical (user-to-admin)\n- Blind IDOR where response doesn't confirm access\n- Time-based IDOR in asynchronous operations\n- IDOR in websocket communications\n\n### Legal Requirements\n- Only test applications with explicit authorization\n- Document all testing activities and findings\n- Do not access, modify, or exfiltrate real user data\n- Report findings through proper disclosure channels\n\n## Examples\n\n### Example 1: Basic ID Parameter IDOR\n```\n# Login as attacker (userId=1001)\n# Navigate to profile page\n\n# Original request\nGET \u002Fapi\u002Fprofile?id=1001 HTTP\u002F1.1\nCookie: session=abc123\n\n# Response: Attacker's profile data\n\n# Modified request (targeting victim userId=1000)\nGET \u002Fapi\u002Fprofile?id=1000 HTTP\u002F1.1\nCookie: session=abc123\n\n# Vulnerable Response: Victim's profile data returned!\n```\n\n### Example 2: IDOR in Address Update Endpoint\n```\n# Intercept address update request\nPUT \u002Fapi\u002Faddresses\u002F5\u002Fupdate HTTP\u002F1.1\nContent-Type: application\u002Fjson\nCookie: session=attacker_session\n\n{\n  \"id\": 5,\n  \"userId\": 1001,\n  \"street\": \"123 Main St\",\n  \"city\": \"Test City\"\n}\n\n# Modify userId to victim's ID\n{\n  \"id\": 5,\n  \"userId\": 1000,  # Changed from 1001\n  \"street\": \"Hacked Address\",\n  \"city\": \"Exploit City\"\n}\n\n# If 200 OK: Address created under victim's account\n```\n\n### Example 3: Static File IDOR\n```\n# Download own receipt\nGET \u002Fapi\u002Fdownload\u002F5 HTTP\u002F1.1\nCookie: session=attacker_session\n\n# Response: PDF of attacker's receipt (order #5)\n\n# Attempt to access other receipts\nGET \u002Fapi\u002Fdownload\u002F3 HTTP\u002F1.1\nCookie: session=attacker_session\n\n# Vulnerable Response: PDF of victim's receipt (order #3)!\n```\n\n### Example 4: Burp Intruder Enumeration\n```\n# Configure Intruder attack\nTarget: PUT \u002Fapi\u002Faddresses\u002F§1§\u002Fupdate\nPayload Position: Address ID in URL and body\n\nAttack Configuration:\n- Type: Battering Ram\n- Payload: Numbers 0-20, Step 1\n\nBody Template:\n{\n  \"id\": §1§,\n  \"userId\": 3\n}\n\n# Analyze results:\n# - 200 responses indicate successful modification\n# - Check victim's account for new addresses\n```\n\n### Example 5: Horizontal to Vertical Escalation\n```\n# Step 1: Enumerate user roles\nGET \u002Fapi\u002Fuser\u002F1 → {\"role\": \"user\", \"id\": 1}\nGET \u002Fapi\u002Fuser\u002F2 → {\"role\": \"user\", \"id\": 2}\nGET \u002Fapi\u002Fuser\u002F3 → {\"role\": \"admin\", \"id\": 3}\n\n# Step 2: Access admin functions with discovered ID\nGET \u002Fapi\u002Fadmin\u002Fdashboard?userId=3 HTTP\u002F1.1\nCookie: session=regular_user_session\n\n# If accessible: Vertical privilege escalation achieved\n```\n\n## Troubleshooting\n\n### Issue: All Requests Return 403 Forbidden\n**Cause**: Server-side access control is implemented\n**Solution**:\n```\n# Try alternative attack vectors:\n1. HTTP method switching (GET → POST → PUT)\n2. Add X-Original-URL or X-Rewrite-URL headers\n3. Try parameter pollution: ?id=1001&id=1000\n4. URL encoding variations: %31%30%30%30 for \"1000\"\n5. Case variations for string IDs\n```\n\n### Issue: Application Uses UUIDs Instead of Sequential IDs\n**Cause**: Randomized identifiers reduce enumeration risk\n**Solution**:\n```\n# UUID discovery techniques:\n1. Check response bodies for leaked UUIDs\n2. Search JavaScript files for hardcoded UUIDs\n3. Check API responses that list multiple objects\n4. Look for UUID patterns in error messages\n5. Try UUID v1 (time-based) prediction if applicable\n```\n\n### Issue: Session Token Bound to User\n**Cause**: Application validates session against requested resource\n**Solution**:\n```\n# Advanced bypass attempts:\n1. Test for IDOR in unauthenticated endpoints\n2. Check password reset\u002Femail verification flows\n3. Look for IDOR in file upload\u002Fdownload\n4. Test API versioning: \u002Fapi\u002Fv1\u002F vs \u002Fapi\u002Fv2\u002F\n5. Check mobile API endpoints (often less protected)\n```\n\n### Issue: Rate Limiting Blocks Enumeration\n**Cause**: Application implements request throttling\n**Solution**:\n```\n# Bypass techniques:\n1. Add delays between requests (Burp Intruder throttle)\n2. Rotate IP addresses (proxy chains)\n3. Target specific high-value IDs instead of full range\n4. Use different endpoints for same resources\n5. Test during off-peak hours\n```\n\n### Issue: Cannot Verify IDOR Impact\n**Cause**: Response doesn't clearly indicate data ownership\n**Solution**:\n```\n# Verification methods:\n1. Create unique identifiable data in victim account\n2. Look for PII markers (name, email) in responses\n3. Compare response lengths between users\n4. Check for timing differences in responses\n5. Use secondary indicators (creation dates, metadata)\n```\n\n## Remediation Guidance\n\n### Implement Proper Access Control\n```python\n# Django example - validate ownership\ndef update_address(request, address_id):\n    address = Address.objects.get(id=address_id)\n    \n    # Verify ownership before allowing update\n    if address.user != request.user:\n        return HttpResponseForbidden(\"Unauthorized\")\n    \n    # Proceed with update\n    address.update(request.data)\n```\n\n### Use Indirect References\n```python\n# Instead of: \u002Fapi\u002Faddress\u002F123\n# Use: \u002Fapi\u002Faddress\u002Fcurrent-user\u002Fbilling\n\ndef get_address(request):\n    # Always filter by authenticated user\n    address = Address.objects.filter(user=request.user).first()\n    return address\n```\n\n### Server-Side Validation\n```python\n# Always validate on server, never trust client input\ndef download_receipt(request, receipt_id):\n    receipt = Receipt.objects.filter(\n        id=receipt_id,\n        user=request.user  # Critical: filter by current user\n    ).first()\n    \n    if not receipt:\n        return HttpResponseNotFound()\n    \n    return FileResponse(receipt.file)\n```\n",{"name":5,"metadata":58,"description":7},{"author":59,"version":60},"zebbern","1.1","main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fidor-testing",3926,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates","https:\u002F\u002Faitmpl.com","https:\u002F\u002Fgithub.com\u002Fdavila7","https:\u002F\u002Fdanielavila.me","Building AI dev tools with LLMs","2026-11-12 14:45:56",{"source":8,"skillName":5,"commands":72,"prompt":82,"zipAvailable":83},[73,76,79],{"tool":74,"command":75},"npx","npx skills add davila7\u002Fclaude-code-templates --skill idor-testing",{"tool":77,"command":78},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill idor-testing",{"tool":80,"command":81},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill idor-testing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fidor-testing\u002FSKILL.md",true,[],[86,112,139,169,203,223],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":93,"publishedAt":53},"01M70NHBTQ8BV0A2SCAZXEPHCX","wealthville-pool-scoring","Score DeFi liquidity pools before providing liquidity. Returns a 0-100 pool score and an Enter\u002FHold\u002FExit\u002FReduce\u002FAvoid verdict with calibrated confidence for ~68,800 Solana pools and 575 EVM pools, plus a public miss-inclusive track record. Use when asked whether a pool is worth LPing into, which pools look best right now, or how accurate the scores have actually been.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fweb-data\u002Fwealthville-pool-scoring\u002FSKILL.md",[92],{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[94,95,96,97,98,35,99,100,101,34,102,103,104,105,106,107,108,109,110,111],"scoring","pool","wealthville pool scoring","liquidity","which","exit","now","use","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":119,"publishedAt":53},"01M70MB6VR8ERJ4EM8D5KHBMEV","technical-debt-auditor","Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO\u002FFIXME\u002FHACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like \"where should I focus refactoring\", \"find code smells\", \"audit my codebase\", \"what technical debt do we have\", \"prioritize cleanup work\", or asks about code quality metrics. Also trigger when the user mentions \"code rot\", \"legacy cleanup\", \"refactoring priorities\", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say \"technical debt\" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ftechnical-debt-auditor\u002FSKILL.md",[118],{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[120,121,122,123,124,125,126,127,128,129,130,34,131,132,133,134,135,136,137,138],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":152,"publishedAt":53},"01M70KPYH9QNHCNME5GJQGE22K","readonly-sql-guard","Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production\u002FERP\u002Fanalytics database (a \"query\" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write\u002FDDL\u002Fside-effect\u002Ftransaction-escape risks. Checks what a statement CALLS, not just its shape.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdatabase\u002Freadonly-sql-guard\u002FSKILL.md",[145,146,147],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":148,"categoryName":149,"taxonomyType":150,"taxonomyTypeDesc":151},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[153,154,155,156,157,158,159,35,160,161,162,163,164,165,166,101,45,167,34,168],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","database","query",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":173,"licenseFileUrl":174,"sourceHtmlUrl":175,"categories":176,"keywords":180,"publishedAt":53},"01M6AFY6F7CC2BBZP1QD6VTNVC","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FSKILL.md",[177],{"categoryNo":178,"categoryName":179,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[181,50,182,183,184,185,186,187,188,189,190,191,192,193,194,195,196,197,198,199,200,201,35,202],"artifacts builder","web artifacts builder","artifacts","builder","state","routing","state management","component","css","frontend","ui","Tools","file","components","shadcn","react","Tailwind","suite","jsx","html","single-file","ui components",{"skillNo":204,"name":205,"nameZh":6,"description":206,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":173,"licenseFileUrl":207,"sourceHtmlUrl":208,"categories":209,"keywords":212,"publishedAt":53},"01M6AFWF33SFV9Z3SF4PEEE4BF","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FSKILL.md",[210,211],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":178,"categoryName":179,"taxonomyType":21,"taxonomyTypeDesc":22},[213,32,214,215,216,50,46,190,191,217,218,219,220,35,221,103,222],"webapp testing","webapp","browser","playwright","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":224,"name":225,"nameZh":6,"description":226,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":173,"licenseFileUrl":227,"sourceHtmlUrl":228,"categories":229,"keywords":237,"publishedAt":53},"01M6AF67Q67JJJ5V51JR2P52KA","discernment-nudge","After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FSKILL.md",[230,233,234],{"categoryNo":231,"categoryName":232,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":235,"categoryName":236,"taxonomyType":150,"taxonomyTypeDesc":151},"01JBSEEDCAT000000000000036","内容创作者",[238,239,240,241,242,243,49,244,183,245,193,131,246,247,248,249,250,165,251,34,252,253,254,255,256,109,257],"discernment nudge","nudge","interpretation","help","run","reasoning","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]