Unrestricted Access to Sensitive Business Flows
A business process such as buying limited stock, booking, signing up or redeeming offers can be automated at scale through the API, with nothing to detect or limit the abuse.
| Severity | Medium |
| CVSS 3.1 | 5.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L Open in the calculator |
| CVSS 4.0 | 5.3 CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-799: Improper Control of Interaction Frequency |
| OWASP Top 10 | A06:2025 Insecure Design |
| Category | Insecure Design |
Description
Some business processes cause harm when they are carried out at machine speed or volume, even though each individual request is legitimate. The API exposes such a flow without anything to tell automated use from human use, or to limit how often one person can complete it, so a script can complete it far faster and more often than any genuine customer. This is not a flaw in the logic of the flow, which works as designed, but a missing design control. It is most visible in APIs because they expose the steps of a flow directly, without the pages, timing and client-side checks that a web interface may add.
Attackers, including resellers and competitors, can use this to buy up limited-availability products and resell them at a higher price, hold reservations for tickets, tables or appointments so that genuine customers cannot book, create large numbers of fake accounts, harvest referral credits, vouchers or free trials, flood the platform with spam, fake reviews or comments, or automate voting. The result is financial loss, damage to customer trust and reputation, and distorted business data, and since each request is legitimate in itself, the abuse can be hard to spot without monitoring designed for it. The impact depends on the value of the flow and the scale an attacker can reach.
The weakness is identified by working with the organisation to list the flows whose abuse would harm the business, then scripting each flow and repeating it rapidly from one account, from several accounts and from several source addresses, and observing whether anything slows, challenges, limits or flags the activity. Testing is kept to quantities agreed with the organisation, so that it does not affect real stock or customers.
Remediation
Identify the flows that need protection, then add layered controls proportionate to the harm that abuse would cause:
- Set business limits per account, payment card, delivery address and device, such as a maximum quantity of a limited item, a limit on reservations held, or one referral reward per verified person.
- Require verified accounts for sensitive flows, for example a confirmed email address or telephone number, and consider waiting periods for new accounts.
- Add friction where automation is likely: a CAPTCHA or similar challenge at key steps, checks on the timing between steps, and queueing for high-demand releases.
- Use device and client signals, such as device fingerprinting and detection of headless browsers and known automation tools, or a bot management service at the edge, to identify automated clients.
- Monitor the flows for unusual patterns, such as many accounts sharing a device, address or payment method, and be able to block and reverse abusive activity.
Confirm the fix by repeating the scripted tests and checking that the controls slow, challenge or block automated use while genuine use remains practical.
References
Add This Finding to Your Library
In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.
Free trialYour trial starts when your portal goes live, not when you sign up, so the time you spend setting up does not count. · No card required
Only need the reporting? Our reporting tool is free and open source, with the same library.