Understanding Application State and Workflow
You'll learn how web applications track user progress through multi-step processes and why understanding these flows is essential for finding business logic vulnerabilities.
What is Application State?
Web applications are inherently stateless — each HTTP request is independent. Yet many features require users to complete multiple steps in order: shopping carts, checkout processes, account registration, password resets, or approval workflows.
To make this work, applications maintain state across requests using:
- Session storage (server-side data tied to a session ID)
- Cookies (client-side tokens)
- Hidden form fields (embedded data passed between pages)
- Database records (order status, workflow stage)
Think of it like a choose-your-own-adventure book where the application remembers which page you're on and what choices you've made so far.
Why Workflows Matter for Security
Multi-step workflows have expected sequences and transitions. For example:
- Browse products → 2. Add to cart → 3. Enter shipping → 4. Enter payment → 5. Confirm order
Attackers look for ways to skip steps, go backward, or jump to later stages without meeting prerequisites. If the application only validates state on the current page but doesn't verify you completed previous steps correctly, vulnerabilities emerge.
Example scenario: Skipping the payment step by directly accessing the "order confirmation" URL, or changing prices in hidden fields during checkout.
Understanding how an application expects users to move through workflows — and what state it tracks at each step — is the foundation for testing business logic flaws like unauthorized state transitions, step manipulation, and workflow bypass attacks.
Key Takeaway:
Application state management tracks user progress across multi-step workflows; security flaws occur when applications fail to validate that all required steps were completed in the proper sequence with valid data.