wstg-business-logic

Tests business logic flaws, workflow bypasses, and file upload weaknesses during penetration tests.

Updated Jul 29, 2026
One-click install
npx skills add https://github.com/MaiconGambini/opencode-harness-guide --skill wstg-business-logic-maicongambini
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wstg-business-logic
Source: https://github.com/MaiconGambini/opencode-harness-guide/tree/main/skills/wstg-business-logic
Command: npx skills add https://github.com/MaiconGambini/opencode-harness-guide --skill wstg-business-logic-maicongambini

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Automated scanners cannot detect business logic vulnerabilities such as forged requests, workflow circumvention, or payment manipulation. This Skill provides a structured methodology based on OWASP WSTG v4.2 to manually identify and exploit these application-specific flaws during security assessments. ## Core Features & Use Cases - Nine Structured Test Cases: Covers data validation, forged requests, integrity checks, process timing, function use limits, workflow circumvention, misuse defenses, and malicious file uploads (WSTG-BUSL-01 through BUSL-09). - Vulnerability Pattern Catalog: Documents common flaw patterns like hidden field trust, premature side effects, predictable identifiers, and extension-only upload validation. - Remediation Guidance: Maps each finding category to concrete fixes such as server-side validation, transaction timeouts, and anti-malware scanning. - Use Case: During a penetration test of an e-commerce platform, use this Skill to test whether discounts can be applied multiple times, whether checkout steps can be skipped, and whether a web shell disguised as an image can be uploaded and executed. ## Quick Start Use the wstg-business-logic skill to test this checkout workflow for business logic flaws including discount reuse, step skipping, and forged request parameters.

Frequently Asked Questions about wstg-business-logic

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?

Map the application's workflows and data handoff points, then use an intercepting proxy to submit logically invalid data, skip workflow steps, and manipulate hidden parameters. Follow the nine WSTG-BUSL test cases covering validation, forging, timing, limits, and uploads.

What are common business logic flaws in e-commerce applications?

Common flaws include applying discounts multiple times by navigating back, skipping checkout steps via URL manipulation, negative quantity or price values, and loyalty points not rolled back on cancellation. These stem from missing server-side state enforcement.

Can automated scanners detect business logic vulnerabilities?

No, automated scanners cannot detect business logic flaws because they require understanding the application's intended functionality and abuse cases. Manual testing with creative misuse scenarios and proxy-based request manipulation is required.

How do I test file upload functionality for security weaknesses?

Submit unexpected file types, spoof Content-Type headers, use double extensions like .php.jpg, and upload the EICAR test file to verify anti-malware scanning. Also test ZIP archives for directory traversal and decompression bombs.

Why does client-side validation fail to prevent business logic abuse?

Client-side validation runs in the browser and is trivially bypassed with an intercepting proxy. Hidden fields, disabled controls, and dropdown restrictions exist only in the DOM, so all business rules must be enforced server-side.