Mutillidae - Insecure Direct Object Reference (Credits)

Mutillidae – Insecure Direct Object Reference (Credits)

In this walk through, we will be going through the Insecure Direct Object Reference (Credits) vulnerability section from Mutillidae Labs. We will be exploring and exploiting Insecure Direct Object Reference (IDOR) in Credits page and learn how application are affected because of it. So, let’s get started with the Hacking without any delay.

Insecure Direct Object Reference (Credits)

Security Level: 0 (Hosed)

  • Setting the security level to 0 or Hosed.

Security level 0

  • The credits page has links to other resources and has a Unvalidated redirect vulnerability as it uses our application URL to redirect to various websites.

Credits page

Burpsuite intercept

  • I intercepted the request and changed the forward url to a hacker simulator website and it worked.

changing parameters

hacker simulator

Also Read: Mutillidae – HTML Injection (User Lookup Xpath)



So, we finally completed all the security levels for the Insecure Direct Object Reference (Credits) Vulnerability. We looked into the various ways how application has been set up in various levels and how we can bypass the security controls implemented. Next, we can mitigate the potential IDOR attacks by implementing access control checks for each object that users are trying to access. The Web frameworks often provide ways to facilitate this. Along with that, avoid exposing identifiers in URLs and GET bodies if possible. Instead, determine the currently authenticated user from session information. On that note, i will take your leave and will meet you in next one with another Mutillidae vulnerability writeup, till then “Keep Hacking”.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top