> 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/password-filtering-via-parameter-controlled-id.md).
# Password Filtering via Parameter Controlled Id
Password Filtering via Parameter Controlled Id notes for PortSwigger Web Security Academy labs, including exploitation workflow, payload testing, Burp Suite validation, and remediation context.
### User ID Controlled by Request Parameter with Password Disclosure
This lab has a user profile page in which the current password appears in a pre-filled field, but masked by a password input. / The user ID is controlled via a parameter in the URL, allowing arbitrary access to the profile of other accounts.
The goal is to retrieve the administrator password, then use it to delete the carlos user.
#### **Procedure Completed**
* Changing the URL parameter can show another user's profile:
```bash
/my-account?id=administrator
```
* The page loads the admin account data well, but the password appears in masked form ( type="password" ).
* Changing the field type in the HTML code on the client side to:
Thus, it is possible to retrieve the administrator's password and connect with it to remove the carlos user from the admin interface.
* the password becomes visible in plain language.
---
# 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/password-filtering-via-parameter-controlled-id.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)