# Sensitive business flow exceeds its permitted frequency or allocation

An actor exceeds an intended recipient, reservation, workflow or tenant allocation through repeated otherwise valid operations.

**Candidate CWE:** [CWE-799](https://cwe.mitre.org/data/definitions/799.html)

## Test hypothesis

Define the product rule and one synthetic recipient or allocation. In a local fixture with recording stubs, compare a permitted operation and the smallest sequence exceeding its configured limit; vary only one entry point, identity budget key, batch form or retry condition at a time.

## Evidence required

Record the intended allocation owner, all fixture identities, requests and committed effects, before/after counters and successful legitimate control. Explain the actual misuse rather than reporting missing automation friction. CWE-799 is a candidate when interaction frequency is the missing control.

## Rule out false positives

Automation, repeated valid actions, absent CAPTCHA or shared quotas may be intentional. Establish a prohibited business outcome; do not send real notifications, purchase scarce inventory or extrapolate unmeasured scale.

## Playbook and command references

- [Resource budgets and sensitive business flows](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/modules/resource-budget-controls.html) — Trace request fan-out, retries, recipient limits and tenant quotas using tiny local limits, recording stubs and measured downstream effects.
- [Workflow invariants, replay, idempotency, and races](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/modules/state-business-logic.html) — Find security consequences in workflow ordering and concurrency, with serial controls and durable-state evidence.

[Find the associated command snippets](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/commands.html?q=Resource%20budgets%20and%20sensitive%20business%20flows)

## Referenced by these target playbooks

[Web & API](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/web-api.html) · [OSS & self-hosted](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/oss.html) · [Cloud & containers](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/cloud.html) · [AI, agents & MCP](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/ai.html)

## Report checklist

- [ ] Capture the affected version, configuration, identities, and object ownership.
- [ ] Preserve a valid baseline and a negative control.
- [ ] Reproduce the forbidden data access, action, or state change on controlled fixtures.
- [ ] Explain the intended security rule and why the observed behavior violates it.
- [ ] State prerequisites, uncertainty, cleanup, and the smallest demonstrated impact.

## Conditional ATT&CK mapping

No direct ATT&CK mapping selected. Record the weakness and demonstrated impact without forcing an adversary-behavior classification. See the [mapping guide](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/attack.html).

## Primary references

- [OWASP API6:2023 sensitive business flows](https://api-security.owasp.org/editions/2023/en/0xa6-unrestricted-access-to-sensitive-business-flows/)
- [CWE-799 interaction frequency](https://cwe.mitre.org/data/definitions/799.html)

[Back to the complete vulnerability catalog](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/vulnerabilities.html)