Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is IDOR?

An insecure direct object reference lets a user reach another user’s data by changing an identifier in a request, because the server never checks who owns the object.

Illustration for the cybersecurity term IDOR
Home / Blog / Cybersecurity Terms / What Is IDOR?
17 November 2026

What Is IDOR?

What Is IDOR?

An insecure direct object reference, almost always shortened to IDOR, is the simplest serious vulnerability in web security. A request contains an identifier that points at a record, the user edits it, and the server returns the record without asking whether that user is entitled to it. Authentication is working perfectly; the missing step is the ownership check.

A Vulnerability You Can Exploit with a Browser

Changing /api/orders/80421 to /api/orders/80422 is the whole technique. It needs no tooling, no payload, and no understanding of the technology stack, which is why it is the most frequently reported class in bug bounty programmes and why it turns up in nearly every API assessment. MITRE tracks it as CWE-639, authorisation bypass through a user-controlled key, and OWASP ranks it first in the API Security Top 10 2023 as broken object-level authorisation.

Identifiers hide in more places than the URL path. Query parameters, JSON bodies, hidden form fields, cookies, custom headers such as a tenant identifier, WebSocket messages, and the sub claim of a token are all equally editable by the client.

The Common Shapes

What It Costs

In September 2022 the Australian telecommunications provider Optus disclosed that an unauthenticated API endpoint had allowed the retrieval of customer records in bulk, affecting around 9.8 million people and exposing passport and driving licence numbers. The technical cause was ordinary: an endpoint reachable without credentials that returned any record by identifier. The follow-on costs, including document reissue for affected customers, ran far beyond the engineering effort a check in the right place would have taken.

In the UK, exposure of this kind is a personal data breach. UK GDPR Article 33 requires notification to the ICO within 72 hours where there is a likely risk to individuals, and Article 34 requires telling the affected people when that risk is high. Access logs that record which identifiers each session requested are what make the scope assessable, and organisations without them generally have to assume the worst case.

Fixing It

  1. Check ownership at the data layer. Scope every query by the authenticated subject, so a repository method takes the user as well as the object identifier and cannot return a record belonging to anyone else.
  2. Centralise the decision rather than writing it per controller, since the one place it is forgotten is the one an attacker finds.
  3. Use indirect references where it fits: a per-session map from a client-facing value to the real identifier, which removes enumeration altogether.
  4. Treat unpredictable identifiers as a hardening measure only. A UUID is harder to guess, and it still leaks through logs, shared links, referrer headers, and other API responses.
  5. Apply the same rule to files. Serve user documents through a handler that performs the check, never from a directory the web server exposes.
  6. Log authorisation failures and alert on patterns, because a sequential walk through identifiers is obvious in the logs if anyone is looking.

Testing for It

Automated scanners perform poorly here, because the tool cannot know that user A should not see user B’s record. Effective testing uses at least two accounts per role, captures the full request set from each, and replays every request with the other session. Burp Suite extensions such as Autorize make the comparison systematic, but someone still has to judge the result. The wider category is covered in broken access control, and the same checks belong in REST API security work. Our web application security testing runs this role matrix across every endpoint rather than a sample.

FAQ – Frequently Asked Questions

Do UUIDs Prevent IDOR?

They prevent enumeration, which is not the same thing. An unpredictable identifier means an attacker cannot simply count upwards, but identifiers leak constantly through browser history, shared links, log files, support tickets, and other API responses that return a list of objects. Once a valid identifier is known, an application without an ownership check still hands over the record.

Is IDOR the Same as Broken Access Control?

IDOR is one specific pattern within that broader category. Broken access control also covers missing function-level checks, forced browsing to hidden pages, privilege escalation through parameter tampering, and policy mistakes. IDOR specifically means the application uses a client-supplied reference to an object without verifying that the caller is entitled to it.

Why Do Scanners Miss These Flaws?

A scanner has no model of who owns what. When it changes an identifier and receives a valid response, it cannot tell whether that response was authorised, because the application returns a normal page either way. Detection requires at least two accounts and a comparison of what each can reach, which means a configured role matrix rather than an unattended scan.

Where Should the Ownership Check Live?

As close to the data as possible. If every repository query is scoped by the authenticated subject, forgetting a check in one controller cannot expose anything, because the query simply returns nothing. Checks written per endpoint rely on every developer remembering every time, and in a codebase of any size one of them will not.

Related Terms

You May Be Interested In These

What Is Just-in-Time Access?

Cybersecurity Terms

17 November 2026

What Is Just-in-Time Access?

Read More
What Is an Authenticated Scan?

Cybersecurity Terms

17 November 2026

What Is an Authenticated Scan?

Read More
What Is Shellshock?

Cybersecurity Terms

17 November 2026

What Is Shellshock?

Read More