testing-for-business-logic-vulnerabilities

Featured

Identifying flaws in application business logic that allow price manipulation, workflow bypass, and privilege escalation beyond what technical vulnerability scanners can detect.

AI & Automation 36,355 stars 4443 forks Updated 2 months ago Apache-2.0

Install

View on GitHub

Quality Score: 94/100

Stars 20%
100
Recency 20%
75
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Testing for Business Logic Vulnerabilities ## When to Use - During authorized penetration tests when automated scanners have found few technical vulnerabilities - When assessing e-commerce platforms for pricing, cart, and payment flow manipulations - For testing multi-step workflows (registration, checkout, approval processes) for bypass opportunities - When evaluating rate-limited features like vouchers, coupons, referrals, and rewards systems - During security assessments of financial applications, voting systems, or any application with critical business rules ## Prerequisites - **Authorization**: Written penetration testing agreement covering business logic testing - **Burp Suite Professional**: For intercepting and modifying multi-step request flows - **Application understanding**: Thorough knowledge of the application's intended business workflows - **Multiple test accounts**: Accounts at different privilege levels and states - **Browser DevTools**: For examining client-side validation logic - **Documentation**: Business requirements or user stories describing expected behavior ## Workflow ### Step 1: Map Business Workflows and Rules Document all critical business processes and their expected constraints. ``` # Critical business flows to map: # 1. Registration/Onboarding flow # - Email verification requirements # - Account approval process # - Role assignment logic # 2. E-commerce/Purchase flow # - Product selection → Cart → Checkout → Payment → C...

Details

Author
mukul975
Repository
mukul975/Anthropic-Cybersecurity-Skills
Created
8 months ago
Last Updated
2 months ago
Language
Python
License
Apache-2.0

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

offensive-business-logic

Business logic vulnerability testing for web/mobile/API engagements. Covers workflow bypass, state machine violations, multi-step process abuse, price/quantity/discount manipulation, currency confusion, coupon stacking, refund/chargeback abuse, race conditions on logic boundaries, parameter tampering for hidden flows, role/tenant boundary violations, time-of-check vs use, anti-automation defeat, fraud-detection evasion, and subscription/quota abuse. Use when scoping an application after surface-level OWASP Top 10 has been covered, or when the asset is a transactional/marketplace/fintech/e-commerce/SaaS app where logic flaws produce direct financial impact.

719 Updated 3 months ago
0xwilliamortiz
AI & Automation Featured

offensive-business-logic

Business logic vulnerability testing for web/mobile/API engagements. Covers workflow bypass, state machine violations, multi-step process abuse, price/quantity/discount manipulation, currency confusion, coupon stacking, refund/chargeback abuse, race conditions on logic boundaries, parameter tampering for hidden flows, role/tenant boundary violations, time-of-check vs use, anti-automation defeat, fraud-detection evasion, and subscription/quota abuse. Use when scoping an application after surface-level OWASP Top 10 has been covered, or when the asset is a transactional/marketplace/fintech/e-commerce/SaaS app where logic flaws produce direct financial impact.

11,204 Updated yesterday
SnailSploit
AI & Automation Listed

sast-businesslogic

Detect business logic vulnerabilities in a codebase using a three-phase approach: threat modeling (domain analysis and attack scenarios), batched verify (check exploitable gaps in parallel subagents, 3 scenarios each), and merge (consolidate batch results). Covers price manipulation, workflow bypass, limit violations, race conditions, reward abuse, etc. Requires sast/architecture.md (run sast-analysis first). Outputs findings to sast/businesslogic-results.md. Use when asked to find business logic, logic flaws, or abuse-of-function bugs.

1 Updated 1 months ago
reasonless-throne486