> 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/access-control/multi-step-process-without-access-control.md).
# Multi Step Process without Access Control
Multi Step Process without Access Control notes for PortSwigger Web Security Academy labs, including exploitation workflow, payload testing, Burp Suite validation, and remediation context.
### Multi-step Process with No Access Control on One Step
The lab offers an administration panel with a multi-step process to change the role of a user. This stream contains a flaw: one of the steps n-aplica no access control. / To train, it is possible to first examine the admin panel with the **administrator:admin** credentials. / To solve the lab, you need to connect with **wiener:peter** and use the vulnerable step to raise your own role to the admin level.
### Process Analysis
The role change occurs in two separate requests:
#### **First Step: Request for Upgrade**
```bash
username=carlos&action=upgrade
```
With the wiener session, this request is refused: / The server indicates that the user is not allowed.
#### **Step 2: Confirmation of Action**
```bash
action=upgrade&confirmed=true&username=carlos
```
This second stage does not include **no access control**. / By sending this request with wiener's session cookie:
The server responds **OK**, although wiener should not have the necessary rights
---
# 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/access-control/multi-step-process-without-access-control.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.
