> For the complete documentation index, see [llms.txt](https://chris26z.gitbook.io/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://chris26z.gitbook.io/home/write-ups/api-pentesting/bola.md).

# BOLA 

BOLA vulnerability occurs when an application or API fails to properly verify if a user is authorized to access specific data objects.. This can allow  users to bypass authorization checks and access sensitive data or perform unauthorized tasks.

this area of the url is vulnerable to BOLA but lets see what is running on the backend to process this info to the frontend side of the site.

<figure><img src="/files/GmPc7QnVpJo5zXnOaRUr" alt=""><figcaption></figcaption></figure>

this area of the url is vulnerable to BOLA and then intercepting the response shows info about alot of information including an id number and full username and email.

<figure><img src="/files/aaJpu2DlaEh4u9HpwDfG" alt=""><figcaption></figcaption></figure>

look for areas say a forums post section or community board can leak info when viewing it in burp or caido. later we can input this into a repeater request by changing the id of the current url. shown in the image below after changing the end of the url it leaks multiple users which can be used to take full control of the infrastructure if an admin was compromised as well.

<figure><img src="/files/EovzE6XLkaMe6yOo6sBx" alt=""><figcaption></figcaption></figure>