Course contentsShow
← Security
Lesson 808 of 3,05217. Web Security - Authorization and Access ControlFree lesson

Multi-Step Process Authorization Failures

Bypassing workflows by skipping or reordering steps when intermediate authorization checks are missing.

Multi-Step Process Authorization Failures

What You'll Learn

You'll discover how attackers bypass multi-step workflows by skipping or reordering steps when applications fail to check authorization at every stage.

The Vulnerability

Many applications implement processes that require multiple steps to complete—think of a checkout flow, password reset, or fund transfer. Developers sometimes make a critical mistake: they only check authorization at the first step, assuming users will follow the intended sequence.

Here's the problem: Attackers can jump directly to later steps or rearrange the order, bypassing security checks entirely.

Analogy: The Security Checkpoint Skip

Imagine a secure facility with three checkpoints:

  1. Sign-in desk (checks your ID)
  2. Metal detector (verifies safety)
  3. Document room (requires clearance)

If only checkpoint 1 verifies your ID, a clever intruder could walk around the building and enter directly through door 3—the document room never checks if you actually passed checkpoints 1 and 2.

Common Attack Scenarios

Password Reset Bypass: An application verifies your identity in step 1, sends a code in step 2, and changes your password in step 3. If step 3 doesn't re-verify who you are, an attacker could directly call the password-change endpoint for any account.

Purchase Process Manipulation: A shopping cart checks payment in step 2 but doesn't verify it again before order confirmation in step 4. Attackers skip step 2 entirely, completing purchases without paying.

Approval Workflow Circumvention: A document approval requires manager sign-off in step 2, but the final publication step (step 3) doesn't check if approval actually happened.

Prevention

Each step in a multi-step process must independently verify:

  • User authorization for that specific action
  • Required previous steps were completed
  • Any state changes are legitimate

Never assume users will follow the intended sequence—enforce it programmatically at every stage.

Key Takeaway: Multi-step processes require authorization checks at every step, not just the first—each stage must independently verify the user has permission and completed prior requirements.