business-logic-vulnerabilities

Tests web applications for business logic flaws including race conditions, price manipulation, and workflow bypass.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/lNwNl/Praxis --skill business-logic-vulnerabilities-lnwnl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: business-logic-vulnerabilities
Source: https://github.com/lNwNl/Praxis/tree/main/skills/business-logic-vulnerabilities
Command: npx skills add https://github.com/lNwNl/Praxis --skill business-logic-vulnerabilities-lnwnl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Business logic vulnerabilities are invisible to automated scanners and require structured human reasoning to uncover. This Skill provides a systematic playbook for finding payment manipulation, race conditions, workflow bypass, coupon abuse, and authorization gaps in authorized web application security assessments. ## Core Features & Use Cases - Attack Playbook: Covers price/quantity tampering, integer overflow, decimal precision exploitation, race conditions (double-spend, coupon reuse), multi-step workflow skipping, and privilege escalation patterns. - Five-Phase Methodology: Business modeling, state machine analysis, a 5×N attack-surface matrix, checklist-driven testing, and human judgement with a Q1-Q7 decision tree. - Module Checklists: Per-module verification items for login, registration, password recovery, payment, coupons, orders, IDOR, captcha, file upload, and CSRF/SSRF/XXE, each with root cause and reproduction steps. - Use Case: During an authorized pentest of an e-commerce platform, use the payment checklist to test negative quantities, decimal skuQty values, and concurrent coupon application with Burp Suite to uncover a 0-yuan purchase flaw. ## Quick Start Use the business-logic-vulnerabilities skill to test this checkout flow for price tampering, race conditions, and payment status forgery.

Frequently Asked Questions about business-logic-vulnerabilities

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

FAQPage Schema
How do I test for business logic vulnerabilities in a web application?▼

Follow the five-phase workflow: model the business roles and assets, map the state machine and data flow, classify attack surfaces in a 5×N matrix, then run per-module checklists. Each item includes the root cause and exact Burp Suite reproduction steps.

How to test payment flows for price manipulation flaws?▼

Intercept checkout requests and tamper with amount, quantity, currency, and discount fields using negative, zero, decimal, and overflow values like 2147483648. Also test dropping required fields, forging payment_status, and replaying payment callbacks without signature verification.

What tools are used for race condition testing?▼

Burp Suite Repeater with Send Group in Parallel and Turbo Intruder with concurrentConnections=30 are the primary tools. They exploit non-atomic check-then-update windows for double-spending gift cards, reusing coupons, and bypassing SMS rate limits.

Can automated scanners detect business logic vulnerabilities?▼

No, business logic flaws lack fixed signatures and depend on application-specific workflows, so scanners miss them. Detection requires manual reasoning about state machines, trust boundaries, and financial impact, which this methodology structures into repeatable steps.

What authorization is required before business logic testing?▼

Written authorization defining target scope, time window, and data access is mandatory. Tests must avoid real personal data, and integer overflow or resource exhaustion tests require secondary confirmation since they can crash production services.