Business Logic Flaw
The application does not enforce the rules of its own processes, so steps can be skipped, repeated or combined in ways that give a user an unintended advantage.
| Severity | Medium |
| CVSS 3.1 | 5.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N Open in the calculator |
| CVSS 4.0 | 5.3 CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-841: Improper Enforcement of Behavioral Workflow |
| OWASP Top 10 | A06:2025 Insecure Design |
| MITRE ATT&CK | T1190 Exploit Public-Facing Application |
| Category | Insecure Design |
Description
Business logic flaws arise when the application accepts each request as valid on its own terms but does not enforce the rules that should govern the process as a whole: the order of steps, the state an object must be in, the limits on a value, or who may act on what. The application assumes that users will follow the path its interface presents, and an attacker who sends requests directly can depart from it.
Typical examples include skipping a step in a multi-stage process, such as going straight to confirmation without completing payment, verification or approval; repeating an action meant to happen once, such as applying a single-use voucher or submitting a refund twice; combining offers that should be exclusive; approving one's own request; acting on an object after it has been locked, cancelled or completed; and supplying values the process never anticipated, such as negative amounts. The impact depends entirely on the process affected. Common outcomes are financial loss through unpaid orders, repeated discounts or refunds, the bypass of verification or approval controls that the organisation relies on, and records left in states that undermine the integrity of later processing or reporting. Exploitation usually needs only an ordinary account and produces activity that looks like normal use, so it can continue unnoticed until reconciliation or audit.
These flaws are identified by manual testing: understanding the intended process and its rules, then reordering, skipping, repeating and altering requests with an intercepting proxy and observing whether the application notices. Automated scanners rarely find them, because they have no model of what the application is supposed to allow, and the requests involved look legitimate to a web application firewall.
Remediation
Enforce the business rules on the server, at the point each action takes effect:
- Model multi-step processes as a server-side state machine: record the state of each order, application or request on the server, and have each step check that the object is in the state it requires before acting, rejecting anything out of sequence.
- Keep process state on the server, tied to the session and the object, rather than in hidden fields, cookies or client-side storage.
- Validate each value against the business rules where it is used, not only at an earlier step: signs, ranges, totals, eligibility, ownership and single-use conditions.
- Make once-only actions atomic, recording that a voucher or refund has been used in the same transaction that applies it.
- Enforce separation of duties, so that users cannot approve their own requests.
- Include abuse cases in design reviews and threat modelling, and turn each one into an automated test.
Monitoring for anomalies, such as unusual discounts, refunds or state changes, provides an interim safeguard while fixes are made. Confirm the fix by repeating the specific sequence that exposed the flaw and checking that the application refuses it.
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.