> 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/unprotected-admin-functionality.md).

# 未受保护的管理员功能

未受保护的管理员功能，PortSwigger Web Security Academy 实验笔记，包括利用流程、载荷测试、Burp Suite 验证以及修复上下文。

### 未受保护的管理员功能

此实验室展示了一个可访问的管理面板，且没有任何形式的访问控制。

#### 目标

删除用户 **carlos** 通过管理界面。

#### 分析

通过探索目录，例如使用 **gobuster**，可以识别隐藏路径：

{% code overflow="wrap" %}

```bash
gobuster dir -u https://0a7a004004ed1cdf8016bc3f0056007f.web-security-academy.net/ -w /usr/share/SecLists/Discovery/Web-Content/common.txt -t 50
```

{% endcode %}

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

该 **robots 文件。txt** 显示了一个指向管理面板的敏感 URL：/ `/administrator-panel`

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

通过直接访问这个未受保护的界面，可以管理用户。/ 只需选择该用户 **carlos** 并删除它。


---

# 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/unprotected-admin-functionality.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.