business-logic-vuln

Routes business logic vulnerability testing across workflow abuse, race conditions, and pricing flaws.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When testing web applications, parser-level injection checks miss flaws rooted in business rules and state machines, such as race conditions, price tampering, and workflow bypasses. This Skill acts as the entry router that directs testing toward those logic-level weaknesses. ## Core Features & Use Cases - Category Routing: Serves as the P1 entry point that decides when business logic testing applies instead of input-injection testing. - Skill Map Navigation: Links to the detailed business-logic-vulnerabilities skill and related routers for API, auth, and file access issues. - Structured Test Flow: Guides mapping of business states and one-time actions, then checking for check-then-act windows, sequence dependencies, and missing cross-step authorization. - Use Case: While assessing an e-commerce checkout flow, use this router to determine whether coupon stacking, negative quantities, or race conditions on inventory should be tested before diving into payload-level attacks. ## Quick Start Ask the agent to evaluate the target application's checkout and coupon workflow for business logic vulnerabilities such as race conditions and price tampering.

Frequently Asked Questions about business-logic-vuln

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?▼

Start by mapping key business states and one-time actions such as payments, approvals, and quota consumption. Then check for check-then-act windows, sequence dependencies, and missing cross-step authorization rather than parser-level input injection.

What is the difference between business logic flaws and injection vulnerabilities?▼

Injection flaws exploit parser-level input handling, while business logic flaws abuse when checks happen and which business conditions are enforced. Logic flaws include race conditions, workflow bypass, price tampering, and stacked discounts.

When should I use a business logic testing router instead of other security checks?▼

Use it when the target involves coupons, inventory, payment, approvals, quotas, invites, trials, or state transitions, and the suspected issue concerns timing or business conditions rather than malformed input parsing.

Can business logic testing combine with API or authentication testing?▼

Yes. When the flaw chain depends on APIs, uploads, or object permissions, the router directs you back to the corresponding api-sec, auth-sec, or file-access-vuln routers to complete the attack path.

What are common examples of race condition vulnerabilities?▼

Common examples include redeeming a one-time coupon multiple times concurrently, double-spending a balance during parallel payment requests, and exhausting inventory limits through simultaneous purchase requests within a check-then-act window.