Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
A business logic flaw is a defect in the rules an application enforces rather than in its code. Every request looks legitimate, which is why scanners almost never find one.

What Are Business Logic Flaws?
A business logic flaw is a defect in the rules an application enforces, not in the code that implements them. Nothing is injected, no memory is corrupted, and every request looks perfectly legitimate in the logs. The attacker simply uses the feature in an order, a quantity, or a combination that the designers never imagined. That is why these defects survive years of automated testing and still turn up in the first week of a manual engagement.
Most logic failures take one of a few recognisable shapes:
In 2015 the researcher Egor Homakov showed that Starbucks gift card balances could be transferred between two cards at the same time. Each transfer read the balance before the other had written its result, so the same funds were credited twice. Repeating the loop turned a small opening balance into a much larger one, and the only unusual thing about the traffic was its timing. The underlying defect was a race condition, but the damage came from the business rule it broke.
A scanner has no way of knowing that a customer may not refund the same order twice, or that a 90% discount should never stack with free delivery. MITRE classifies the whole family under CWE-840, which is a category rather than a pattern, precisely because there is no signature to match. The OWASP Web Security Testing Guide devotes section 4.10 to business logic, with tests for data validation, request forging, integrity checks, process timing, and function misuse. Each one assumes the tester has read the specification first.
Abuse cases belong in design, alongside the happy path. A short threat modelling session that asks how each rule could be turned around catches more of this class than any tool.
Logic flaws in payment journeys sit close to the Financial Conduct Authority’s strong customer authentication rules, where skipping or replaying an authentication step has regulatory weight as well as financial cost. Where a flaw lets one customer reach another customer’s records, it becomes a personal data breach, and UK GDPR requires notification to the ICO within 72 hours of becoming aware of it. Our web application security testing works from your own process documentation, so the rules are tested as written rather than as guessed.
Very rarely. A scanner judges responses against generic patterns such as error messages or reflected input, and a logic flaw produces a perfectly normal response. The request that drains a balance looks like the request that tops it up. Finding these defects needs a human who understands the business rules, usually working from a specification, several test accounts, and a request interception proxy.
Broken access control is about who may act on which object. A business logic flaw is about what the application allows anyone to do, including the legitimate owner of the account. A user who refunds their own order three times is not reaching another person’s data at all, yet the outcome is still a loss. In practice the two often appear together in the same workflow.
Process documentation, however rough: the states an order or application can occupy, the limits that apply, who may approve what, and which actions are meant to be single use. Two or three accounts at different privilege levels help, as does a test environment where money movements are simulated. Without this, testers can only guess at the intended rules.
No. Because they abuse intended functionality, they tend to be fully reliable and easy to automate once found, and they often map directly onto money or entitlement. A discount that can be applied repeatedly, or a withdrawal that can be doubled, causes measurable loss from the first attempt and is difficult to distinguish from genuine activity afterwards.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.