idor

Tests web applications for IDOR vulnerabilities through object ID manipulation and access control bypass techniques.

Updated Sep 17, 2026
One-click install
npx skills add https://github.com/karenrebecag/spec-driven-standards --skill idor-karenrebecag
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: idor
Source: https://github.com/karenrebecag/spec-driven-standards/tree/main/plugins/security/skills/offensive-idor
Command: npx skills add https://github.com/karenrebecag/spec-driven-standards --skill idor-karenrebecag

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Broken access control and Insecure Direct Object Reference (IDOR) flaws are among the most common and highest-impact web vulnerabilities, yet they require systematic manual testing that is easy to do incompletely. This Skill provides a structured, end-to-end IDOR hunting methodology so pentesters and bug bounty hunters don't miss test cases. ## Core Features & Use Cases - Systematic IDOR Discovery: Guides account setup, traffic interception, parameter tampering (numeric IDs, GUIDs, encoded/encrypted IDs, arrays, JSON objects), and horizontal/vertical privilege escalation testing. - Bypass & Evasion Techniques: Covers HTTP method switching, parameter pollution, path normalization, outdated API versions, mass assignment, and request smuggling to defeat weak protections. - Modern Surface Coverage: Includes GraphQL, gRPC, presigned cloud URLs, WebSockets, OAuth/OIDC flows, MFA endpoints, and CI/CD detection tooling (Burp extensions, Pynt, StackHawk, RESTler). - Use Case: During a bug bounty engagement, you intercept a request like GET /api/documents/123. The Skill walks you through swapping IDs, testing encoded variants, chaining with information disclosure, and documenting a reproducible proof of concept. ## Quick Start Ask the assistant to walk you through testing an intercepted API request for IDOR vulnerabilities using the offensive-idor checklist.

Frequently Asked Questions about idor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test for IDOR vulnerabilities in a web application?

Create two accounts per role, intercept sensitive requests with a proxy like Burp Suite, and swap object IDs in URLs, bodies, and headers between accounts. If switching IDs grants access to another user's data or actions, you have found an IDOR.

What tools are used for IDOR and BOLA detection?

Burp Suite extensions like Autorize, AuthMatrix, and Auto Repeater compare responses across user roles. CI-native scanners such as Pynt and StackHawk auto-generate BOLA test cases, while Arjun helps discover hidden parameters.

Can IDOR exist when applications use GUIDs or hashed IDs?

Yes. GUIDs and hashed IDs only provide obfuscation, not authorization. Test by decoding base64 or hex values, harvesting leaked IDs from API responses, error messages, or JavaScript, and checking whether the server actually validates ownership.

Does IDOR testing apply to GraphQL and gRPC APIs?

Yes. In GraphQL, swap id arguments in queries, mutations, and batched requests while checking per-field authorization. For gRPC, use grpcurl and fuzzers to manipulate IDs in binary messages and verify authorization on every method.

What is the difference between horizontal and vertical IDOR?

Horizontal IDOR accesses resources of other users at the same privilege level, such as another customer's orders. Vertical IDOR reaches resources requiring higher privileges, like administrative endpoints, by manipulating identifiers or parameters.

When should IDOR testing not be performed?

Only test systems you own or have explicit written authorization to assess, such as in-scope bug bounty targets. Automated enumeration of IDs against production systems without permission can violate laws and terms of service.