> 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/user-id-controlled-by-unpredictable-guid-parameter.md).

# 由不可预测 GUID 参数控制的用户 ID

由不可预测 GUID 参数控制的用户 ID，PortSwigger Web Security Academy 实验笔记，包括利用流程、载荷测试、Burp Suite 验证以及修复上下文。

#### 由参数控制的用户 ID

本实验展示了一个 **水平权限提升** 问题，出现在用户账户页面。/ 其特殊之处在于 **用户通过 GUID 进行标识**，也就是较长且随机的凭证，例如：

```bash
9e2f3fc0-7035-48ed-ad6d-f643690c7b9d
```

连接到账户后 **wiener:peter**，你可以在“我的账户”部分看到自己的 GUID。

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

#### **通过公开内容恢复 GUID**

通过浏览网站，我们可以在 **可见的发布内容中找到** 其他用户的 GUID：

* 管理员的 GUID 出现在他的一篇帖子中。

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-d3986f80c0b30028730db5f85d5c799ecb875646%2Fimage%20(269).png?alt=media" alt=""><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-7a67cce120c504b0da7e8cc1a7789bf06cbcbb1b%2Fimage%20(270).png?alt=media" alt=""><figcaption></figcaption></figure>

```bash
?userId=5abc76d3-7763-4be9-83d1-c6181bcdf0b5
```

#### **操作：访问 Carlos 账户**

该账户页面可通过一个可控参数访问：

```bash
my-account?id=5abc76d3-7763-4be9-83d1-c6181bcdf0b5
```

只需将我们的 GUID 替换为 **carlos**，我们就能访问他的账户：

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-6215ffb1c858fefb2e9f8b36c932c2079f2fda1c%2Fimage%20(271).png?alt=media" alt=""><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/user-id-controlled-by-unpredictable-guid-parameter.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.
