Quick answer
Broken object level authorization (BOLA), also known as insecure direct object reference (IDOR), is a flaw where an application lets you access a record just by changing its identifier in a request, without checking that the record belongs to you. It is ranked the number one risk in the OWASP API Security Top 10 and is behind many large data exposures.
On this page
How It Works
An API call such as GET /api/invoices/10457 returns your invoice. If the server only checks that you are logged in, and not that invoice 10457 is yours, changing the number to 10458 returns someone else's. The same applies to account numbers, file names, order IDs and user IDs in URLs, request bodies and headers. Sequential numbers make it trivial to download every record, but random identifiers are not a fix on their own if they leak elsewhere in the application.
Why It Matters
BOLA flaws are easy to exploit, hard for automated scanners to find, and often expose an entire customer database rather than one record. Several well-known breaches involved APIs that returned customer data for any identifier supplied. Because the requests look normal, they rarely trigger security alerts.
How to Test for It
- Map every API endpoint that accepts an object identifier, including in bodies, headers and GraphQL queries.
- Create two test accounts, then try to read, change and delete each account's objects using the other account's session.
- Test every role and tenant boundary, not just user against user.
- Check whether identifiers are predictable and whether they leak in other responses, links or emails.
- Check whether bulk or rapid sequential access triggers rate limits or alerts.
How to Reduce the Risk
Enforce an ownership or permission check on the server for every request that touches an object, implemented once in a shared authorization layer rather than repeated per endpoint. Use unpredictable identifiers as defense in depth, rate limit and monitor enumeration patterns, and include cross-account tests in automated testing and every penetration test.
Regulatory and Framework Context
In the US, BOLA and IDOR flaws have led to enforcement actions over exposed customer data, and the FTC expects reasonable security for consumer information, including testing APIs that serve it.
Being exploited now
Threat Radar →The latest related vulnerabilities confirmed as exploited in the wild.
- CVE-2026-119977·2 weeks ago·Web appsWordPress WordPress CoreWordPress WordPress Core Time-of-check Time-of-use (TOCTOU) Race Condition VulnerabilityEPSS 1.6%
- CVE-2026-48356·3 weeks ago·Web appsAdobe Commerce and MagentoAdobe Commerce and Magento Unrestricted Upload of File with Dangerous Type VulnerabilityEPSS 47.5%
- CVE-2026-109618·3 weeks ago·Web appsPHP Group PHPPHP Memory Corruption VulnerabilityEPSS 100.0%
- CVE-2026-109619·3 weeks ago·Web appsPHP Group PHPPHP Stale Internal Request-State VulnerabilityEPSS 100.0%
Common questions
Is BOLA the same as IDOR?
Essentially yes. IDOR is the older web application term; BOLA is the name used in the OWASP API Security Top 10 for the same missing ownership check.
Why don't vulnerability scanners find BOLA?
Scanners do not know which records belong to which user. Finding BOLA needs a tester with multiple accounts who understands the business logic.
Do random IDs fix BOLA?
They make guessing harder but do not fix the missing check. If an identifier leaks anywhere, the record is exposed.
For testers: finding write-ups
How this shows up in a penetration test report, with severity, verification and remediation, in the StrikeOps Findings Library.
Change log
- November 13, 2026First published.