> For the complete documentation index, see [llms.txt](https://hacking-notes.jord4n.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hacking-notes.jord4n.pro/web/business-logic/failed-state-machine-workaround.md).
# Failed State Machine Workaround
Failed State Machine Workaround notes for PortSwigger Web Security Academy labs, including exploitation workflow, payload testing, Burp Suite validation, and remediation context.
### Authentication Bypass via Flawed State Machine
This lab is based on incorrect assumptions about the sequence of steps in the authentication process. By using this poorly designed state machine it is possible to bypass authentication, access the administration interface and delete the user **carlos**.
Identifier provided:
* **User:** wiener
* **Password:** peter
**Observation principale**
The connection flow is cut into several successive steps, including an intermediate role selection step.
The application assumes that all steps are executed in the order and that each request has been properly validated before proceeding to the next one.
**Operation stages**
1. Connection with valid `wiener:peter` credentials.
2. After login, the application proposes a step of **role selection**.
* Click forward to move forward.
* At the time of GET request to the **role selector**, intercept the request.
**Do not let the request go**: block or delete it ( drop ).
* It is at this stage that validation of the role is carried out.
Continue the flow without this validation.
**Result**
The application wrongly considers that all steps have been properly validated. / The user accesses the \*\* admin panel\*\* directly, without having selected or validated a legitimate role.
From there it is possible to remove the user **carlos** and validate the lab.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://hacking-notes.jord4n.pro/web/business-logic/failed-state-machine-workaround.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
