api-boplalisted
Install: claude install-skill AnandJogawade/Zazy-Pentest-Plugin-for-Claude
# API3 — Broken Object Property Level Authorization (BOPLA)
Merges Excessive Data Exposure (read too much) and Mass Assignment (write too much) at the object-property level. Points ref: `${CLAUDE_PLUGIN_ROOT}/payloads/INJECTION-POINTS.md`.
## Trigger phrases
`api3, bopla, mass assignment, excessive data exposure, hidden fields, over-disclosure, autobind, property level authorization`
## Method
1. **Excessive data exposure** — inspect **raw** API responses, not the UI. Hunt fields the UI never renders: `isAdmin`, `role`, `passwordHash`, `balance`, internal flags, other users' data embedded in list objects, PII beyond what's shown.
2. **Map writable fields** — diff what you send vs. what `GET` returns to enumerate the object schema (also from OpenAPI/`graphql`/APK).
3. **Mass assignment** — inject hidden/privileged fields into `POST`/`PUT`/`PATCH`:
```http
PATCH /api/users/self {"email":"x@x","isAdmin":true}
POST /api/orders {"items":[...],"price":0,"status":"paid"}
```
target: `isAdmin`/`role`/`is_verified`/`account_balance`/`price`/`discount`/`user_id`/`tenant_id`/`approved`.
4. **Probe writability** — send an invalid value (`"isAdmin":"foo"`) and watch for a changed response/error implying the field reaches query logic.
5. Re-`GET` the object (or log in again) to confirm the privileged field actually persisted.
## Bypass / evasion
Try nested paths (`{"user":{"isAdmin":true}}`), array wrapping, snake_case vs camelCase variants, and conten