Sovra Recon·Glossary · Business Logic

Business Logic Vulnerabilities: Definition, Examples, and Detection

By Solan Barlet, co-founder of Sovra Recon
Updated October 29, 2026

In short

A business logic vulnerability is an error in an application’s operational rules, not in its technical code: the application does exactly what it’s told to do, but not what the company intended. Ordering a negative quantity, skipping the payment step, combining incompatible discounts: each request appears normal; it’s the sequence of actions that is abusive. These vulnerabilities have no signature and therefore evade automatic scanners.

Typical examples

Type of vulnerabilityExample
Trust in the customerThe price or discount is sent by the browser and accepted as-is by the server
Unexpected ValuesA negative quantity reduces the total cart value; a decimal amount circumvents a limit
Bypassing the User FlowDirectly accessing the order confirmation page without going through the payment step
Improperly Combined RulesA reusable promo code, or one that can be combined with an offer that was supposed to exclude it
Assumptions About the UserA feature reserved for verified accounts remains accessible before verification

Why don’t the scanners detect them?

A scanner looks for known patterns: an SQL error, a reflected script, a vulnerable version. A logic vulnerability produces none of these signals—the response is a normal success. Recognizing it requires understanding what the application is supposed to do, then figuring out how to circumvent its rules, which falls under the realm of penetration tests.

MITRE classifies these vulnerabilities under CWE-840 (Business Logic Errors).

How to Protect Against It

  • Recalculate everything that has a value on the server side: prices, discounts, fees, and quantities.
  • Enforce the correct sequence of steps on the server side, not just in the user interface.
  • Describe the business rules and their abuse scenarios from the design phase onward, then test them.
  • Log and monitor abnormal behavior (unusual discounts, zero-amount orders).

Frequently asked questions

Can a business logic vulnerability be serious?

Yes: it often directly affects money (payments, discounts, credits) or access rights. Its severity depends on what the circumvented rule was protecting.

Sources

Find out where an attacker would get in.

Our AI agents actually attack your scope, fully automated, and hand you the proof of every vulnerability.