Insights on Crypto Payments, Infrastructure, and Operations

Broken Object Level Authorization (BOLA)

Abbreviation: BOLA

Pronunciation: BROH-kun AHB-jehkt LEH-vul aw-thur-uh-ZAY-shun (B-O-L-A)

Also known as: Broken Object Level Authorization, BOLA

Definition

BOLA is an API vulnerability where changing an object identifier lets a user access or modify another user's protected resource. Broken Object Level Authorization occurs when an API accepts a user-controlled object identifier but fails to verify that the authenticated requester may access that specific object.

Overview

Meaning and scope

BOLA is an API vulnerability where changing an object identifier lets a user access or modify another user’s protected resource. Broken Object Level Authorization occurs when an API accepts a user-controlled object identifier but fails to verify that the authenticated requester may access that specific object.

Mechanism and operation

Targets can include accounts, invoices, wallets, documents, transactions, or administrative records. An attacker may replace an identifier in a path, query, or request body and receive another user’s data or perform unauthorized changes. Every function that reads or changes an object should enforce ownership or policy checks using trusted server-side context. Tests should compare access across users, roles, and tenants, while monitoring looks for sequential probing, repeated denials, and unusual cross-account access. For Broken Object Level Authorization (BOLA), teams should measure unnecessary friction, exclusion, delay, privacy intrusion, failed recovery, and inconsistent treatment while preserving the safeguards needed for material payment and commerce exposure.

Practical payment example

A malicious customer changes the order ID in an API request and sees another merchant’s invoice; server-side ownership checks must reject the call.

Operational checks

For Broken Object Level Authorization (BOLA), the trust decision should establish BOLA is an API vulnerability where changing an object identifier lets a user access or modify another user’s protected resource and bind the result to the requested action and protected resource. Teams should test issuance, storage, validation, expiry, revocation, recovery, and privileged override for permissions and protected actions, rather than checking only a successful request.

Distinctions and limits

Random-looking identifiers reduce guessing but do not replace server-side authorization because identifiers can leak through logs, links, or other responses. BOLA is prevented by checking permission on every requested object, not by hiding or randomizing object identifiers.

Related definitions: Authorization.

Example

A malicious customer changes the order ID in an API request and sees another merchant’s invoice; server-side ownership checks must reject the call.

Comparison

Random-looking identifiers reduce guessing but do not replace server-side authorization because identifiers can leak through logs, links, or other responses. BOLA is prevented by checking permission on every requested object, not by hiding or randomizing object identifiers.

Key Takeaway

BOLA is prevented by checking permission on every requested object, not by hiding or randomizing object identifiers.

Sources

  1. NIST Documentation: Cyberframework — NIST (2026-07-30)
  2. OWASP Documentation: Www Project Api Security — OWASP (2026-07-30)
  3. OWASP Official Documentation — OWASP (2026-07-30)