[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CC2WBR8BSXDVMWFSRWT9VM":3,"skill-same:01M6CC2WBR8BSXDVMWFSRWT9VM":74},{"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":26,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":14,"repositoryHtmlUrl":55,"repositoryHomepageUrl":6,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M6CC2WBR8BSXDVMWFSRWT9VM","IDOR Vulnerability 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.","Gabriellmaia01\u002Fneuro-dose-assist","Gabriellmaia01","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F135177180?v=4","01M6CBRZEZC8G5C400AG3SPFNH","Gabriel","01M6CBRZK8MB7DWW0B4C82TV2G",0,"MIT","https:\u002F\u002Fgithub.com\u002FGabriellmaia01\u002Fneuro-dose-assist\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fskills\u002Fidor-testing\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[27,5,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"testing","idor","vulnerability","guidance","exploit","user","broken","find","direct","access","applications","ids","authorization","data","web","test","vulnerabilities","2026-11-10 10:12:30",false,"---\nname: IDOR Vulnerability 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":49,"description":7},{"author":50,"version":51},"zebbern","1.1","main","eac60cc6e0b6baa2a05a765a851fb10638f4e733",".agent\u002Fskills\u002Fskills\u002Fidor-testing","https:\u002F\u002Fgithub.com\u002FGabriellmaia01\u002Fneuro-dose-assist","https:\u002F\u002Fgithub.com\u002FGabriellmaia01","https:\u002F\u002Fportfolio-bice-theta-81.vercel.app\u002F","💻 Desenvolvimento De Software_\r\n\r\n⚙️ Engenharia De Software\r\n","2026-11-12 08:51:23",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add Gabriellmaia01\u002Fneuro-dose-assist --skill \"IDOR Vulnerability Testing\"",{"tool":66,"command":67},"bunx","bunx skills add Gabriellmaia01\u002Fneuro-dose-assist --skill \"IDOR Vulnerability Testing\"",{"tool":69,"command":70},"pnpm","pnpm dlx skills add Gabriellmaia01\u002Fneuro-dose-assist --skill \"IDOR Vulnerability Testing\"","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGabriellmaia01\u002Fneuro-dose-assist\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fskills\u002Fidor-testing\u002FSKILL.md",true,[],[75,99,120,140,151,172],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":84,"publishedAt":44},"01M6CCFWA9JJ23708FSKK1QNBW","zapier-make-patterns","No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points.  This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power","https:\u002F\u002Fgithub.com\u002FGabriellmaia01\u002Fneuro-dose-assist\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fskills\u002Fzapier-make-patterns\u002FSKILL.md",[81],{"categoryNo":82,"categoryName":83,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[85,86,87,88,89,90,91,92,93,94,95,96,97,98],"zapier make patterns","writing","workflow","automation","code","apache","how","automate","integrations","business","use","simplicity","power","complexity",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":109,"publishedAt":44},"01M6CCFSBPM49S618W7G4NHH13","Cross-Site Scripting and HTML Injection Testing","This skill should be used when the user asks to \"test for XSS vulnerabilities\", \"perform cross-site scripting attacks\", \"identify HTML injection flaws\", \"exploit client-side injection vulnerabilities\", \"steal cookies via XSS\", or \"bypass content security policies\". It provides comprehensive techniques for detecting, exploiting, and understanding XSS and HTML injection attack vectors in web applications.","https:\u002F\u002Fgithub.com\u002FGabriellmaia01\u002Fneuro-dose-assist\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fskills\u002Fxss-html-injection\u002FSKILL.md",[105,106],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":107,"categoryName":108,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[110,111,112,113,114,27,115,116,37,117,31,118,41,42,43,32,119],"injection","scripting","html","site","Cross Site Scripting and HTML Injection Testing","html injection testing","cookies","xss","content","security",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":135,"publishedAt":44},"01M6CCFJ9XTPXHTE4JR06WY475","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002FGabriellmaia01\u002Fneuro-dose-assist\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[126,127,130],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":128,"categoryName":129,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":131,"categoryName":132,"taxonomyType":133,"taxonomyTypeDesc":134},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[86,136,137,138,139,95],"writing skills","deployment","work","editing",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":148,"publishedAt":44},"01M6CCFG98EMZZ43D1CPZZZ54E","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002FGabriellmaia01\u002Fneuro-dose-assist\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[146,147],{"categoryNo":128,"categoryName":129,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":131,"categoryName":132,"taxonomyType":133,"taxonomyTypeDesc":134},[86,149,150,89,95],"writing plans","spec",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":158,"publishedAt":44},"01M6CCFDPACVC9ZM8TN63MGBP5","workflow-automation","Workflow automation is the infrastructure that makes AI agents reliable. Without durable execution, a network hiccup during a 10-step payment flow means lost money and angry customers. With it, workflows resume exactly where they left off.  This skill covers the platforms (n8n, Temporal, Inngest) and patterns (sequential, parallel, orchestrator-worker) that turn brittle scripts into production-grade automation.  Key insight: The platforms make different tradeoffs. n8n optimizes for accessibility","https:\u002F\u002Fgithub.com\u002FGabriellmaia01\u002Fneuro-dose-assist\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fskills\u002Fworkflow-automation\u002FSKILL.md",[157],{"categoryNo":82,"categoryName":83,"taxonomyType":21,"taxonomyTypeDesc":22},[159,88,87,160,161,162,163,164,90,165,166,167,168,169,170,171],"Workflow Automation","network","ai agents","accessibility","workflows","infrastructure","flow","Production","execution","inngest","parallel","orchestrator","resume",{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":179,"publishedAt":44},"01M6CCFB0KAB0PPNV38XQPX6YX","WordPress Penetration Testing","This skill should be used when the user asks to \"pentest WordPress sites\", \"scan WordPress for vulnerabilities\", \"enumerate WordPress users, themes, or plugins\", \"exploit WordPress vulnerabilities\", or \"use WPScan\". It provides comprehensive WordPress security assessment methodologies.","https:\u002F\u002Fgithub.com\u002FGabriellmaia01\u002Fneuro-dose-assist\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fskills\u002Fwordpress-penetration-testing\u002FSKILL.md",[178],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[27,174,180,181,119,43,182,183,32,95,31,184,185],"penetration testing","wordpress","assessment","plugins","pentest","security assessment"]