The following is a guest blog post from Mert & Evren, two talented researchers from Turkey. IDOR vulnerabilities are of the higher impact and higher paying vulnerabilities for web bug bounties. This article explores what IDORs are and how to find them.

What is authorization in web/mobile applications?

Web/mobile applications’ session management is very important for end users. Session management consists of two important parts, authentication and authorization. The authentication part is the answer of the “WHO AM I?” question and the authorization part is the answer of the “WHAT CAN I DO?” question.

If we explain with the simplest approach, we are observing the authorization stages on Linux operating system file rights specified as write, read and execute. If a user wants to write a file, that the user must be given the “w” authority. If not used correctly, there are some privacy violations.

What is an IDOR vulnerability?

There can be many variables in the application such as “id”, “pid”, “uid”. Although these values are often seen as HTTP parameters, they can be found in headers and cookies. The attacker can access, edit or delete any of other users’ objects by changing the values. This vulnerability is called IDOR.

First, it needs to understand the application flow developed by the software developers. All the modules functions and their sub-modules functions need to be understood when the logged-in user into the web/mobile application. It is also important to remember that this vulnerability is as severe as XSS, CSRF in security testing and as a type of vulnerability that is not easily discovered (automatized testing or manual testing).

The IDOR vulnerability is illustrated in the following image between user and server.

In this article, the following topics will be addressed:

  • How to find the injection point that IDOR vulnerabilities can be found?
  • Some IDOR vulnerability tips that seem to be quite simple and the best experiences we have encountered.
  • Precautions to taking into consideration while IDOR vulnerability is testing.
  • How to provide basic authorization controls?

Effective & fast IDOR vulnerability test

You can use the browser’s secret tab to quickly practically test IDOR vulnerabilities. So, when you use the regular tab as a normal user, you can use the secret tab as an attacker. This will ensure that you don’t logout.

You can use Burp Suite’s HTTP History tab for checking all of requests. The HTTP History feature that shows all the traffic between the device (browser, phone, tablet) and the application’s server. Also, you can use Burp Suite’s scope feature for fast testing. Because the scope feature can be useful to make a target list and the scope feature allows showing only relevant data for your testing scope.

For example; the company “Bugcrowd” that we tested and the scope is only given as “” on the scope page. In this case, you can add the relevant scope by right-clicking on a request.

You can edit this added scope value according to the given scope as follows:

Finally, you should do the following filtering in the HTTP History tab by selecting “Show only in-scope items”.

These will help you to understand roles like readonly, normal, super etc in the application better.

Capture all requests!

When IDOR vulnerability testing, basically, you need to perform make all the requests that the web/mobile application should be create. Because if you changed something in the application, can create other requests using this case. If you have all API requests of the application like WSDL file, Swagger page etc. and it’s working regularly, you’re in luck! You can use this and it’ll give you convenience for IDOR testing.

An example is encountered in a private program. Credit cards are added when made the purchase in the mobile application. After the requests are tested, it can be thought that there is not any vulnerability. But when a made second purchase, credit card selection screen is seen and the IDOR vulnerability is at this point. When selecting a credit card on here, application will send the credit card id to server in a request and this request did provide to access other users’ credit cards data changing the credit card id.

In another private program, the web application included an in-app messaging system. The user could send messages to other users and add other users to own messages. When the user tries to access one of own messages, a request went to “/messages/5955” and own message id seems to be “5955”. Likewise, when trying to access another user’s message by making a request to “/messages/5955”, the message was not accessed. When the user wanted to add another user to own message, arises a request like the one below.

POST /messages/5955/invite HTTP/1.1Host: example.comUser-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Firefox/52.0Accept: */*X-Requested-


XMLHttpRequestCookie: my_cookiesConnection: closeuser=testaccount2

And when this request is examined, the user can add itself to other users’ messages and access all messages.

In addition, roles in the application must be well understood in order to identify IDOR vulnerability. If you know what that a role should do or should not do, it will be very useful during the phase of weakness detection. So firstly, you should understand the application deeply!

How to find injection points?

As before say, you can find many requests for IDOR vulnerability testing using all features of application. When API endpoints are not provided in IDOR vulnerability tests, .html source code or .js files are useful. These files include interesting things and ajax requests usually. IDOR vulnerability testing can be performed using presented requests in these files. This can be requests made earlier by the application, and possible future requests.

If you are lucky, you can see only the requests that an authorized, admin user should see in javascript files. Because of this, source code and especially javascript files should analyze well.

Also, you can search web application’s old version on “” and you may can find useful requests in old javascript files or you can search requests in search engines using dorks.

In some cases, id values aren’t unique like 1, 2, 3, 100, 1000 etc, these id values can be encoded or hashed value. If you face an encoded value, you can test the IDOR vulnerability with decoding the encoded value. If you face a hashed value, you should test whether the hash value is an accessible or predictable value. In another case, you can access hashed value in “Referrer“ header, so these scenarios can be replicated.

For example, you can’t access the another users’ objects but you can find object’s hashed id value in the object page’s source code, you can find the object’s hashed id into an in-app message from victim user (this will decrease the impact of bug). So you can create 2 test accounts as X and Y, then try to X’s hashed id value in Y’s requests in Burp History.

If we will touch another topic, some applications’ requests may scare you. For example, the SmartSheet’s request that contains more than one parameter appears to be too complex.

If you wanna find the inject point in this request, you can use Burp Suite’s compare tool. You should right-click on the request and choose “Send to Comparer” option. Then you can create the same request for using another object and send to comparer.

When you visit to the comparer tool and click on the “Words” button, you will be presented with a window where the changing points.

You can use same method for HTTP responses and you can examine their differences.

Interesting cases for IDOR bugs

Manipulate the create requests

Some applications create an id on client-side and then send the in create request to server. This id value can be number such as “-1”, “0” or anything. The existing id values change with the previously created objects’ id. So you can delete / edit other users’ objects using IDOR vulnerability.

If you do not see a parameters like “id”, “user_id”, “value”, “pid”, “post_id” while creating an object, you should add it and test it yourself. You can find the parameter key name by deleting or editing any object on app.

Blind IDOR

In another case, you can find an IDOR vulnerability but you may couldn’t realize of that. For example, if you change the object’s informations in app, you’ll get an email that includes the object’s information. So if you try to change another user’s informations of object, you can’t access anything in HTTP response but you can access the informations of object with an email. You can call it “Blind IDOR”. 🙂

Combine them!

IDOR bugs’ impacts are changeable and we’ll touch on that. In some cases, IDOR vulnerabilities can help you by triggering other vulnerabilities that can not be exploited. If you find an unimportant IDOR vulnerability such as editing users non-public & unimportant filename and you wanna raise the impact of your bug, you can use self-XSS bug. The self-XSS vulnerability that you found while the web application testing is generally out of scope and not rewarded. However, you can combine self-XSS vulnerability with another IDOR vulnerability and you can submit report as “IDOR + Stored XSS”. In this way you can achieve a vulnerability of P2 level.

Critical IDORs

IDOR vulnerability allows us to access an account at some time, rather than to edit or delete it. These critical bugs appear in fields such as password reset, password change, account recovery. So firstly, you should double check the link in your email and parameters in it. Then, you can capture the password reset request and examine the parameters with any proxy tool. We have seen many times the “user id” value in these requests and we could takeover to another user’s account easily.

At the same time, it’s an important thing that’s account takeover by header values sent in the request. It is seen that some header values such as “X-User-ID”, “X-UID” from the test and debug environments are changed. So that the user can act like any user and was able to account takeover successfully.


In rare cases, you can test the HPP (HTTP Parameter Pollution) vulnerability for IDOR testing by adding the same parameter one more time in your request. An example of this:

Create valid request

You should sure that the request send to the server is correct. If you try send the a user’s request with an other user, you must sure that the this request’s “CSRF-Token” value is valid. So you should put the other user’s “CSRF-Token” to in the request. Otherwise, you will get an error because of token values do not match. This can make you mislead.

Likewise, if your tested request is XHR (XML HTTP Request), you must check the validation of “Content-Type” header parameter in your request. Also, app’s requests may have custom headers like “W-User-Id”, “X-User-Id”, “User-Token” etc. If you wanna do a correct and perfect test, you must send all headers that used by app is correct.

Useful tools

As we mentioned before, you can use Burp Suite features. Also, you can use Burp Suite plugins for IDOR vulnerability testing, such as “Authz”, “AuthMatrix” and “Authorize”.

The Authz plugin provides to see response of requests for another users. So you can send X user’s request to Authz and try to access response of it as Y user. Also, you can add custom header for the testing IDOR vulnerability like “X-CSRF-Token”. You can get it from the BApp Store or in this address.

The AuthMatrix plugin allows you to perform authorization checks by registering cookie values or header values for roles in the application. You can get it from the BApp Store and if you want more information for this nice plugin, go here.

If you have API requests, you can use Wsdler plugin for Burp Suite, SoapUI, Postman etc. You can try all GET, POST, PUT, DELETE, PATCH requests and success and fast API test using the tools.

Impact of IDOR vulnerabilities

IDOR vulnerabilities seems as “VARIES DEPENDING ON IMPACT” in Bugcrowd VRT because of their impact totally depend your submitted bug.

But we have created a list about IDOR vulnerabilities’ impacts based on our experience as follows.

P1 – Account takeover, Access very important data (such as credit card)

P2 – Change / delete another users’ public data, Access private / public important data (such as tickets, invoice, payment information)

P3 – Access / delete / change private data (limited personal info: name, adress etc.)

P4 – Access any unimportant data

IDOR vulnerabilities’ impact depends on the discretion of the program manager.

How to prevent IDOR vulnerabilities?

First, you should control all normal, ajax and API requests when creating an app. For example, can read-only user write anything in app? Or can non-admin user access and create API token that only created by admin user? So, for the test all of IDOR vulnerabilities, you should think like a hacker.

You can provide permission on your application for all endpoints. If your “privatesection” endpoint includes the API requests such as “/api/privatesection/admins”, “/api/privatesection/console”, “/api/privatesection/tokens”, you can block the endpoint for non-admin users.

Also, to make the attacker’s job harder and even sometimes even to prevent it, you can use hash function and use hashed values instead of normal number or strings.