Insecure Direct Object Reference
Also called IDOR.
Accessing others' objects by changing an identifier in a request.
What it is
An access-control flaw where an application exposes a reference to an internal object (like a record ID), and fails to verify the requester is authorized for it. Changing the identifier reveals data belonging to others.
Why it matters
IDOR is a leading cause of mass data exposure because it is trivial to exploit by incrementing identifiers. It is a focused instance of broken access control that testers probe early.
In practice
Changing the invoice ID in a URL to a sequential value returns another customer's invoice instead of the requester's own.
What to look for
- Sequential IDs in URLs or API calls.
- Access to records that belong to other users.
- API responses that return data without an ownership check.
Common mistake
Hiding IDs with random values. Random IDs slow attackers down but do not replace an access check.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
- Risk Scoring
Score a vulnerability with CVSS v3.1, or an incident across five dimensions, and see the reasoning behind each number.
- Map and Score
Map real procedures to ATT&CK techniques, then pick the CVSS v3.1 metrics for real vulnerabilities.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Burp Suite Commercial
An intercepting proxy for testing web apps by hand and with its scanner.
-
ZAP Open source
An open source web app scanner and proxy, often run in CI pipelines.
-
Cloudflare WAF Commercial
Blocks common web attacks at the edge while the code gets fixed.
Read next
- Broken Access Control: Failure to enforce what authenticated users are allowed to do.
- SQL Injection: Injecting SQL through input to manipulate a database query.
- Path Traversal: Using crafted paths to reach files outside the intended directory.