> 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/change-role-in-user-profile.md).
# Change Role in User Profile
Change Role in User Profile notes for PortSwigger Web Security Academy labs, including exploitation workflow, payload testing, Burp Suite validation, and remediation context.
### User Role Can Be Modified in User Profile
This lab contains an administration panel located at **/admin**, accessible only to connected users with a **roleid = 2**. / The mission is to modify our own role, access the admin interface and delete user **carlos**.
1. We connect with the credentials provided:/ **wiener: peter**
2. In the profile section, the email address change is sent via a JSON request, for example:
```json
{
"email":"jordan@test.com"
}
```
The answer returns this data directly to JSON, which shows that no strict filtering is applied.
By injecting an additional parameter **roleid**, we test:
```json
{
"email":"jordan@test.com",
"roleid": 2
}
```
5. The server accepts this change and returns a **302 Found**, confirming that our role has been changed to **2**.
6. Once promoted administrator, we have access to **/admin**, where just use the functionality to **delete user carlos** and thus solve 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/access-control/change-role-in-user-profile.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.
.png?alt=media)
.png?alt=media)