Insecure direct object reference meaning, in plain words

IDOR, insecure direct object reference, lets someone see another person's data by changing a number. How it works, its link to BOLA, and what OWASP advises.

Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated

IDOR means changing a number is enough to see someone else's information. Its full name is insecure direct object reference. OWASP describes it as a state in which a reference to an internal object, such as an order number or file name, is exposed on screen without checking whether the requester has permission.

How does IDOR work?

Imagine a hospital where card numbers run in sequence, and saying a different number at the counter brings out another person's chart. Anyone can say a number, but the counter is supposed to check whether it is that person's chart.

OWASP breaks IDOR into three ingredients: the object, a reference that points to it, and the missing check of permission to the object. With the check missing, a user who merely swaps the number they were shown for another can reach someone else's data.

In APIs, the same problem is called BOLA (broken object level authorization). The OWASP API Security Top 10 ranked it first in its 2023 edition. CWE-639 lists IDOR and BOLA as related names, but their scope does not fully match. The treatment in APIs is organized on the BOLA vulnerability page.

Why does IDOR matter?

It is a flaw that operators find hard to notice, because the screen shows nothing wrong and login was done correctly. IPA also points out that where the design takes a user ID or order number through the URL or similar, a logged-in person can act as someone else.

Things managed by number, such as member information, order history, and invoice PDFs, are many on a member site. Because personal information is involved, even a single leak damages trust.

OWASP's preventive measure is to check permission every time data is touched. It also lists narrowing the search range to the current user's own data.

Identify the user from the session, not from a value sent from the screen. A random identifier is only an aid. Its place is explained under broken access control. The free URL check is the quick way to see what an outsider sees of your pages.

Related terms

Frequently asked questions

Are IDOR and BOLA the same thing?

They point at close problems but are not exactly the same. CWE-639 lists IDOR and BOLA as related names, but their scope does not fully match. IDOR is used more often for web screens and BOLA for APIs.

Does using random strings instead of numbers prevent IDOR?

No. OWASP says random identifiers are only an aid that makes guessing harder and do not replace access control. You need to check on every access that the person is allowed.

Next step

The IDOR-type problem in APIs is organized on the BOLA vulnerability page, and the whole order for protecting login is in unauthorized access measures. The free URL check shows only what is visible from outside, and for how your member data is handled, contact us.

Frequently asked questions

Are IDOR and BOLA the same thing?

They point at close problems but are not exactly the same. CWE-639 lists IDOR and BOLA as related names, but their scope does not fully match. IDOR is used more often for web screens and BOLA for APIs.

Does using random strings instead of numbers prevent IDOR?

No. OWASP says random identifiers are only an aid that makes guessing harder and do not replace access control. You need to check on every access that the person is allowed.

See what an attacker can see, today

The free URL check returns a grade in under a minute. For costs and next steps, book a free consultation.