> 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/access-control-based-on-the-referer-header.md).
# Access Control Based on the Referer Header
Access Control Based on the Referer Header notes for PortSwigger Web Security Academy labs, including exploitation workflow, payload testing, Burp Suite validation, and remediation context.
### Referer-based Access Control
This lab applies a access control to administration features based on the header **Referer**. / You can first explore the administration panel by connecting with **administrator:admin** credentials.
To solve the lab, you need to log in with user **wiener:peter** and use the wrong validation of the Referer to get an admin role.
#### **1. Context**
* Session cookie for *wiener*
```bash
cIA2AyZn2GhizvLK7VR8SUCMcdezZcFl
```
* When attempting to change roles without additional header, the application refuses access:
```http
GET /admin-roles?username=wiener&action=upgrade HTTP/2
Host: 0a19008c034b40de834b14e0009a0062.web-security-academy.net
Cookie: session=cIA2AyZn2GhizvLK7VR8SUCMcdezZcFl
```
The answer indicates that the user does not have the necessary rights.
#### **2. Bypassing the Referer Check**
If one adds a header **Referer** pointing to a legitimate admin page, the application accepts the operation
```bash
Referer: https://0a19008c034b40de834b14e0009a0062.web-security-academy.net/admin
```
With this added header, promotion of wiener becomes possible and admin access is obtained.
---
# 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/access-control-based-on-the-referer-header.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.
