> 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/bypassing-access-control-based-on-http-method.md).
# Bypassing Access Control Based on HTTP Method
Bypassing Access Control Based on HTTP Method notes for PortSwigger Web Security Academy labs, including exploitation workflow, payload testing, Burp Suite validation, and remediation context.
### Method-based Access Control Can Be Circumvented
In this lab, access controls are partly based on the HTTP method used. After connecting with *administrator:admin* credentials, the administration panel can be freely observed.
The goal is to connect with *wiener:peter* credentials and exploit the wrong implementation of the control to assign the role of administrator.
After connecting as an administrator, we discover the interface to increase or decrease the privileges of a user. / By intercepting the request sent during a modification:
```http
POST /admin-roles
username=carlos&action=upgrade
```
This action requires administrative fees when sent in **POST**.
However, when attempting to reproduce this request with the wiener session, the application returns a refused access message.
However, if the POST method is replaced by **GET**, the control fails:
```http
GET /admin-roles?username=wiener&action=upgrade
```
This request passes and returns a **200 OK**, which allows to raise the privileges of wiener to the rank of administrator.
---
# 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/bypassing-access-control-based-on-http-method.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.
