> 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/ja/web/access-control/user-id-controlled-by-parameter.md).

# パラメータで制御されるユーザーID

パラメータで制御されるユーザーIDの PortSwigger Web Security Academy ラボ向けノート。攻撃フロー、ペイロードテスト、Burp Suite による検証、および是正策の文脈を含みます。

### リクエストパラメータで制御されるユーザーID

このラボでは **水平権限昇格** ユーザーアカウントページ上の問題です。/ このラボを解くには、次を取得する必要があります： **carlos のユーザー API キー** それを解答として送信してください。/ 次の認証情報で接続できます： **wiener:peter**.

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

自分のユーザーパネル（wiener のもの）では、アカウントIDがURLパラメータで送信されていることがわかります。

たとえば、このパラメータを変更して自分のIDを carlos に置き換えると：

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

するとページには carlos のアカウント情報が表示され、その \*\*APIキー\*\* を取得できます。

<figure><img src="https://2001299964-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-dc12988a68052766c57783b17d62e136521f1985%2Fimage%20(267).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/ja/web/access-control/user-id-controlled-by-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.
