business-logic-vuln

Audit business workflows for state-transition and multi-step logic vulnerabilities.

120|8|Updated Jun 2, 2026
One-click install
npx skills add https://github.com/Prohao42/aimy-sikll --skill business-logic-vuln-prohao42
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: business-logic-vuln
Source: https://github.com/Prohao42/aimy-sikll/tree/main/ai-mian/hack-skills/skills/business-logic-vuln
Command: npx skills add https://github.com/Prohao42/aimy-sikll --skill business-logic-vuln-prohao42

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Business logic vulnerabilities arise when state transitions and multi-step workflows are not properly validated, enabling workflow bypass, race conditions, pricing flaws, or state-desynchronization.

Core Features & Use Cases

  • Map key business states and one-time actions to surface risky transitions.
  • Detect check-then-act windows, sequence dependencies, and missing cross-step authorization.
  • Route to related router skills for API access, uploads, or permission checks to complete the path.

Quick Start

Identify the target workflow's states and run a state-transition audit to reveal race conditions and logic gaps

Frequently Asked Questions about business-logic-vuln

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

FAQPage Schema
What is a business logic vulnerability and how do state transitions create risk?

A business logic vulnerability occurs when multi-step workflows lack proper validation, allowing workflow bypass. Risk arises when state transitions and check-then-act windows are exploited to bypass security controls like pricing or quotas.

How do I test for race conditions in multi-step workflows?

To test for race conditions in multi-step workflows, map key business states and one-time actions. Running a state-transition audit reveals sequence dependencies and check-then-act windows that create exploitable logic gaps.

How can I detect missing cross-step authorization in ordering systems?

Detect missing cross-step authorization by mapping the ordering system's states and one-time actions. Audit the process to verify that authorization checks are properly enforced across all state transitions and multi-step sequences.

Does this approach work for testing coupon systems and pricing flaws?

Yes, this approach works for testing coupon systems and pricing flaws. It identifies risky transitions and check-then-act windows in processes involving pricing, quotas, and approvals to surface exploitable state-desynchronization issues.

Can I coordinate API access checks with this state-transition audit?

Yes, you can coordinate API access checks. The state-transition audit routes to related router skills to verify API access, uploads, and permissions, completing the path to identify cross-step authorization weaknesses.