The vulnerability manifests in profile viewing functionality where user-controlled ID parameters (e.g., /user/3) are used to retrieve user records. In MVC frameworks like Kohana (which Gleez CMS uses), this would typically map to a view action in the User controller. The lack of authorization checks before displaying sensitive profile information matches the IDOR pattern described. The high confidence comes from: 1) The URL structure matching common MVC routing patterns 2) The vulnerability's direct relationship to profile viewing functionality 3) The CWE-639 classification indicating missing authorization on user-controlled keys 4) The reproduction steps showing direct parameter manipulation in the URL path.