> 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/zh/web/access-control/password-filtering-via-parameter-controlled-id.md).

# 通过参数控制 ID 进行密码过滤

通过参数控制 ID 进行密码过滤，PortSwigger Web Security Academy 实验笔记，包括利用流程、载荷测试、Burp Suite 验证以及修复上下文。

### 用户 ID 受请求参数控制并泄露密码

这个实验室有一个用户资料页面，其中当前密码出现在预填充字段中，但被密码输入框隐藏。/ 用户 ID 通过 URL 中的参数进行控制，从而允许任意访问其他账户的资料。

目标是获取管理员密码，然后使用该密码删除 carlos 用户。

#### **操作已完成**

* 更改 URL 参数可以显示另一个用户的资料：

```bash
/my-account?id=administrator
```

* 页面正确加载了管理员账户数据，但密码以隐藏形式显示（type="password"）。
* 将客户端 HTML 代码中的字段类型更改为：

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-8ab8ef10282645cec6bf4e4445657a9fbb8ab3e8%2Fimage%20(277).png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

因此，可以获取管理员的密码，并使用它登录以在管理员界面中删除 carlos 用户。

* 密码就会以明文显示。

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-383d5be149b7fa435377da7d30e93a7c2e2f19be%2Fimage%20(278).png?alt=media" alt="" width="563"><figcaption></figcaption></figure>


---

# 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/zh/web/access-control/password-filtering-via-parameter-controlled-id.md?ask=<question>&goal=<user_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.
