<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/bola-enumerating-an-entire-employee-directory-through-a-predictable-id-5lh2ad7fu" -->

---
title: BOLA: Enumerating an Entire Employee Directory Through a...
description: A gray-box penetration test of a corporate SaaS HR platform uncovered a Broken Object Level Authorization (BOLA) flaw in an endpoint that accepted a plain...
canonical: https://daily.dev/posts/bola-enumerating-an-entire-employee-directory-through-a-predictable-id-5lh2ad7fu
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: BOLA: Enumerating an Entire Employee Directory Through a Predictable ID | daily.dev
og:description: A gray-box penetration test of a corporate SaaS HR platform uncovered a Broken Object Level Authorization (BOLA) flaw in an endpoint that accepted a plain...
og:url: https://daily.dev/posts/bola-enumerating-an-entire-employee-directory-through-a-predictable-id-5lh2ad7fu
og:image: https://api.daily.dev/og/posts/5lH2Ad7Fu.png
og:image:alt: BOLA: Enumerating an Entire Employee Directory Through a Predictable ID
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# BOLA: Enumerating an Entire Employee Directory Through a Predictable ID

**[InfoSec Write-ups](https://daily.dev/sources/infosecwriteups)** · 6 min read · 0 upvotes · 0 comments

## Summary

A gray-box penetration test of a corporate SaaS HR platform uncovered a Broken Object Level Authorization (BOLA) flaw in an endpoint that accepted a plain sequential integer (idPersonnal) to fetch employee records, without verifying the caller had any relationship to that record. By simply incrementing the ID, a low-privilege authenticated session could dump the entire employee directory, including names, department, supervisor, tax IDs, and — because the response also included email and plaintext password fields — working login credentials for every employee, enabling account takeover. The endpoint had no rate limiting, making the whole directory trivially scriptable. Remediation involves enforcing server-side object-level authorization checks tying the requested ID to the caller's identity or role before returning data.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://infosecwriteups.com/bola-enumerating-an-entire-employee-directory-through-a-predictable-id-2fa11370e919>

## Questions this post answers

### What is a Broken Object Level Authorization (BOLA) vulnerability and how does it differ from IDOR?

BOLA is the API-specific form of IDOR, where an endpoint uses a client-supplied identifier to fetch an object but the server never verifies the caller actually owns or is entitled to that object. It ranks as API1:2023 in the OWASP API Security Top 10 because APIs lack the visual cues, like a disabled button, that hide similar flaws in UIs.

_Teams hardening API authorization models can track BOLA writeups and OWASP guidance on daily.dev._

### How can a sequential integer ID in an API request lead to a full data breach?

When an endpoint trusts a client-supplied sequential integer, such as idPersonnal, as the sole lookup key without checking the caller's entitlement, an attacker can simply increment or decrement the value to retrieve other users' records. In one documented case, this exposed names, tax IDs, supervisors, and even plaintext passwords for an entire employee directory, with no rate limiting to slow the enumeration.

_Developers auditing endpoints for IDOR-style exposure can follow real-world exploit breakdowns on daily.dev._

### How do you fix a BOLA vulnerability in an API endpoint?

Enforce object-level authorization on every request that includes an identifier: before returning any record, verify the authenticated user either owns that specific ID or holds an explicit role-based grant, such as an HR/admin role, to view records outside their own. Sensitive fields like passwords or emails should also never be serialized back to non-privileged roles.

_Engineers writing authorization checks into API handlers can find hands-on BOLA remediation patterns on daily.dev._

## Similar posts on daily.dev

- [Everyone Knows About Broken Authorization – So Why Does It Still Work for Attackers?](https://daily.dev/posts/everyone-knows-about-broken-authorization-so-why-does-it-still-work-for-attackers--exddy4tnt) · Security Boulevard · 1 upvotes · 0 comments
- [The 5 Most Disastrous API Vulnerabilities](https://daily.dev/posts/the-5-most-disastrous-api-vulnerabilities-aehrfktvw) · Nordic APIs · 0 upvotes · 0 comments
- [Agents Turn Broken Auth Into a Breach at Machine Speed](https://daily.dev/posts/agents-turn-broken-auth-into-a-breach-at-machine-speed-ew6xjsbnf) · API Evangelist · 0 upvotes · 0 comments
- [Why AI Agents Write Broken Access Control](https://daily.dev/posts/why-ai-agents-write-broken-access-control-7drb4bp0v) · Snyk · 1 upvotes · 0 comments
- [Beyond Authentication — Exploiting a Nasty IDOR in Profile Update Functionality](https://daily.dev/posts/beyond-authentication-exploiting-a-nasty-idor-in-profile-update-functionality-9g5il2oa7) · InfoSec Write-ups · 0 upvotes · 0 comments

---

Tags: [#security](https://daily.dev/tags/security), [#authorization](https://daily.dev/tags/authorization)

[View this post on daily.dev](https://daily.dev/posts/bola-enumerating-an-entire-employee-directory-through-a-predictable-id-5lh2ad7fu)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"BOLA: Enumerating an Entire Employee Directory Through a Predictable ID","url":"https://daily.dev/posts/bola-enumerating-an-entire-employee-directory-through-a-predictable-id-5lh2ad7fu","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/bola-enumerating-an-entire-employee-directory-through-a-predictable-id-5lh2ad7fu"},"datePublished":"2026-09-08T16:02:21.928Z","dateModified":"2026-09-08T16:02:50.772Z","description":"A gray-box penetration test of a corporate SaaS HR platform uncovered a Broken Object Level Authorization (BOLA) flaw in an endpoint that accepted a plain...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/b697b10b186740cd622558e44e302941?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/b697b10b186740cd622558e44e302941?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"InfoSec Write-ups","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"InfoSec Write-ups","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/f0dc21b5bbfd46fda36f7b4b53dd1705","url":"https://daily.dev/sources/infosecwriteups"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/bola-enumerating-an-entire-employee-directory-through-a-predictable-id-5lh2ad7fu","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"security,authorization","timeRequired":"PT6M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"InfoSec Write-ups","item":"https://daily.dev/sources/infosecwriteups"},{"@type":"ListItem","position":3,"name":"BOLA: Enumerating an Entire Employee Directory Through a Predictable ID"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/bola-enumerating-an-entire-employee-directory-through-a-predictable-id-5lh2ad7fu#faq","mainEntity":[{"@type":"Question","name":"What is a Broken Object Level Authorization (BOLA) vulnerability and how does it differ from IDOR?","acceptedAnswer":{"@type":"Answer","text":"BOLA is the API-specific form of IDOR, where an endpoint uses a client-supplied identifier to fetch an object but the server never verifies the caller actually owns or is entitled to that object. It ranks as API1:2023 in the OWASP API Security Top 10 because APIs lack the visual cues, like a disabled button, that hide similar flaws in UIs. Teams hardening API authorization models can track BOLA writeups and OWASP guidance on daily.dev."}},{"@type":"Question","name":"How can a sequential integer ID in an API request lead to a full data breach?","acceptedAnswer":{"@type":"Answer","text":"When an endpoint trusts a client-supplied sequential integer, such as idPersonnal, as the sole lookup key without checking the caller's entitlement, an attacker can simply increment or decrement the value to retrieve other users' records. In one documented case, this exposed names, tax IDs, supervisors, and even plaintext passwords for an entire employee directory, with no rate limiting to slow the enumeration. Developers auditing endpoints for IDOR-style exposure can follow real-world exploit breakdowns on daily.dev."}},{"@type":"Question","name":"How do you fix a BOLA vulnerability in an API endpoint?","acceptedAnswer":{"@type":"Answer","text":"Enforce object-level authorization on every request that includes an identifier: before returning any record, verify the authenticated user either owns that specific ID or holds an explicit role-based grant, such as an HR/admin role, to view records outside their own. Sensitive fields like passwords or emails should also never be serialized back to non-privileged roles. Engineers writing authorization checks into API handlers can find hands-on BOLA remediation patterns on daily.dev."}}]}
```

