business-logic-attack

Detect business logic vulnerabilities in e-commerce transactional flows.

1.6k|234|Updated Dec 7, 2019
One-click install
npx skills add https://github.com/wgpsec/AboutSecurity --skill business-logic-attack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: business-logic-attack
Source: https://github.com/wgpsec/AboutSecurity/tree/main/skills/exploit/business-logic-attack
Command: npx skills add https://github.com/wgpsec/AboutSecurity --skill business-logic-attack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Web applications often fail to enforce business rules in server-side logic, allowing attackers to manipulate transactions, orders, and accounts.

Core Features & Use Cases

  • Detects price/amount manipulation in payments, quantity manipulation, order-status tampering, coupon/discount abuse, and race-condition risks in transactional flows.
  • Provides practical testing steps to reproduce business logic flaws in e-commerce or financial-like apps.
  • Use case: testing a checkout flow where changing order_id or price could bypass payments or alter orders.

Quick Start

Simulate price/amount and quantity changes in the checkout flow to verify server-side validation.

Frequently Asked Questions about business-logic-attack

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a business logic vulnerability in web applications?

A business logic vulnerability is a flaw in an application's server-side rule enforcement, allowing attackers to manipulate transactional flows, payments, or account statuses without exploiting technical vulnerabilities.

How do I test e-commerce checkout flows for parameter tampering?

You test e-commerce checkout flows by simulating price, quantity, and order_id changes in payment requests to verify if the server correctly validates the submitted data and prevents unauthorized alterations.

How can I detect coupon abuse and discount manipulation in payment systems?

Detect coupon abuse by manipulating discount parameters and coupon codes in transactional flows to verify if the application properly validates user eligibility, usage limits, and server-side authentication.

Does this method require technical vulnerability exploitation to find order flaws?

No, this testing method requires no technical vulnerability exploitation, instead validating server-side checks, authentication, and input validation across e-commerce endpoints to detect order and payment logic flaws.

What is the best way to test race conditions in transactional web applications?

Test race conditions by sending concurrent requests targeting transactional flows and order processing endpoints to verify if the application enforces proper locking and prevents duplicate or unauthorized order submissions.

Can I use this approach to test account-related endpoints for improper authorization?

Yes, you can apply this approach to account-related endpoints by tampering with input parameters to detect improper authorization and confirm whether the server validates user permissions across all requests.