business-flow

Tests authenticated business logic endpoints for IDOR, authorization bypass, and stored XSS.

2|1|Updated Aug 28, 2026
One-click install
npx skills add https://github.com/lycheer1126/xs-bigdan --skill business-flow-lycheer1126
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: business-flow
Source: https://github.com/lycheer1126/xs-bigdan/tree/main/knowledge/skills/business_flow
Command: npx skills add https://github.com/lycheer1126/xs-bigdan --skill business-flow-lycheer1126

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Authenticated business features (OA, CRM, e-commerce, workflow apps) hide high-impact flaws like horizontal privilege escalation, payment state manipulation, and stored XSS that generic scanners miss. This Skill turns 113 field-tested action fragments into a repeatable methodology for systematically walking every authenticated function point. ## Core Features & Use Cases - Four-Question Framework: For every function point, ask whether the server trusts a value, whether limits are frontend-only, whether object IDs can be swapped (IDOR), and whether content is re-rendered (XSS), with prioritized attack actions per question. - Path Discovery & Enumeration: Covers hidden routes, half-authenticated endpoint fuzzing (401 vs 404 differential), cookie/session creation analysis, and same-vendor pattern migration to map the authenticated attack surface before testing. - Payment & Privilege State Machines: Documents type-flipping, order ID substitution, free-channel-to-paid-content access, and concurrency abuse against quotas, with explicit compliance thresholds (e.g., max 5 IDOR proof records, 0.01-value test payments). - Use Case: Given a target CRM with test accounts in scope, walk each menu operation, capture request/response pairs, swap userId/orgId parameters between two accounts, and log findings as structured FINDING lines with request/response evidence. ## Quick Start Activate this skill when the BRIEF contains test accounts or cookies and the target is in the linkage or deep phase, then walk each authenticated function point through the four-question framework.

Frequently Asked Questions about business-flow

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

FAQPage Schema
How do I test for IDOR vulnerabilities in authenticated APIs?

Replace object identifiers such as userId, orgId, fileId, phone numbers, or emails in requests with values belonging to another account, then compare responses between two test accounts you control. Stop after confirming with at most five real records as evidence.

What is the four-question framework for business logic testing?

For each function point ask: does the server trust this value, is the limit enforced frontend-only, can this object be swapped for someone else's, and will this content be re-rendered. Test in that priority order since object swapping yields the highest finding rate.

How do I find hidden authenticated endpoints in a web application?

Run authenticated fuzzing with tools like ffuf and use 401 versus 404 response differentials to detect existing endpoints. Also enumerate SPA route tables, probe paths like /admin or /test, and diff network traffic when switching pages.

When should this business flow testing approach be used?

Use it only after reconnaissance completes and test credentials or cookies are available, typically in linkage or deep testing phases against business-heavy targets like CRM or e-commerce systems. It requires explicit authorization and defined scope.

What are the compliance limits for payment and SMS testing?

Payment tests use 0.01-value orders on your own accounts with cancellation afterward. SMS or email bombing checks stop after at most three variant requests, and concurrency tests stay under 50 threads against test accounts only.