api-authorization-and-bola

Tests API endpoints for BOLA, function-level authorization flaws, and mass assignment vulnerabilities.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/lNwNl/Praxis --skill api-authorization-and-bola-lnwnl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: api-authorization-and-bola
Source: https://github.com/lNwNl/Praxis/tree/main/skills/api-authorization-and-bola
Command: npx skills add https://github.com/lNwNl/Praxis --skill api-authorization-and-bola-lnwnl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? APIs frequently expose object identifiers, nested resources, and hidden writable fields without proper authorization checks, allowing attackers to access or modify other users' data. This Skill provides a focused, repeatable testing playbook to systematically uncover Broken Object Level Authorization (BOLA), Broken Function Level Authorization (BFLA), and mass assignment flaws. ## Core Features & Use Cases - Structured Test Loop: Guides a two-account methodology (Account A vs Account B) to replay create, read, update, and delete flows across authorization boundaries. - Test Surface Coverage: Targets object reads, nested resources, admin functions, alternate HTTP verbs, and hidden JSON fields like role, org, verified, and tier. - Quick Payloads & Routing: Supplies ready-to-use mass assignment payloads and routes to related skills for JWT abuse, GraphQL discovery, and broader IDOR patterns. - Use Case: During a web CTF or authorized penetration test, you discover an endpoint like /api/v1/orders/123. Use this Skill to replay the request with a second account's token, test PUT/PATCH/DELETE variants, and inject hidden fields such as {"role":"admin"} to escalate privileges. ## Quick Start Use the api-authorization-and-bola skill to test the target API's object endpoints for BOLA and hidden field authorization flaws using two accounts.

Frequently Asked Questions about api-authorization-and-bola

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test an API for BOLA vulnerabilities?▼

Create two accounts, capture Account A's create/read/update/delete requests, then replay them with Account B's token against the same object IDs. Also test sibling endpoints, nested resources, and alternate HTTP verbs on the same routes.

What is mass assignment in API security testing?▼

Mass assignment occurs when an API blindly binds client-supplied JSON fields to server-side objects, letting attackers set hidden fields like role, isAdmin, org, or verified. Test by injecting these fields into update requests and observing privilege changes.

What API endpoints are most likely to have authorization flaws?▼

Endpoints exposing object IDs such as /api/v1/orders/123, nested resources like /users/1/invoices/9, admin functions, and update paths using PUT, PATCH, or DELETE are prime targets. IDs hidden in headers, cookies, and GraphQL arguments are also commonly missed.

Why do nested API resources often have broken authorization?▼

Developers frequently validate access on the parent resource but omit checks on child resources, assuming the parent check is sufficient. Testing each nested level independently with a second account's token reveals these gaps.

When should I use a different skill instead of this BOLA playbook?▼

Use the JWT abuse skill when the weakness lies in token handling rather than object access, the GraphQL skill for hidden parameter discovery, and the IDOR skill for broader object authorization patterns outside API contexts.