> 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/dom/dom-based-open-redirection.md).

# DOM-Based Open Redirect

DOM-Based Open Redirect notes for PortSwigger Web Security Academy labs, including exploitation workflow, payload testing, Burp Suite validation, and remediation context.

### DOM-based Open Redirection

This lab contains an open redirection vulnerability on the DOM side. The goal is to exploit this vulnerability to redirect the victim to the exploit server.

**Vulnerable Fragment (back to blog button)**/ The action code associated with the button in the comments section is:

{% code overflow="wrap" %}

```javascript
onclick='returnUrl = /url=(https?:////.+)/.exec(location); location.href = returnUrl ? returnUrl[1] : "/"'
```

{% endcode %}

<figure><img src="https://131707722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-bb7fc6d8de75ba3ef5f65e0ebfe5b0f8a827c4f5%2F%7B1424D7A8-D049-42F4-B8B1-47FA143FBA38%7D.png?alt=media" alt=""><figcaption></figcaption></figure>

This script extracts a `URL` parameter from the current URL using a regular expression and redirects to its value if it exists; Otherwise it returns to the root (`/`).

**Operating principle**/ Simply add `&URL=<target>` to the post URL. When the user clicks on "back to blog", the script recovers this parameter and the browser is redirected to the supplied target.

**URL examples**

{% code overflow="wrap" %}

```
https://0a9700fa04b783118073038f00bc00eb.web-security-academy.net/post?postId=1&url=https://jord4n.pro
```

{% endcode %}

* — after loading, click back to blog redirects to `https://jord4n.pro`.

<figure><img src="https://131707722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-b763ccbee5665d9583bbd2f88b79d9f9c913822b%2F%7B77876782-7E83-4C36-8766-5A11B5AC71AB%7D.png?alt=media" alt=""><figcaption></figcaption></figure>

For the lab (direct to the exploit server):

{% code overflow="wrap" %}

```
https://0a9700fa04b783118073038f00bc00eb.web-security-academy.net/post?postId=1&url=https://exploit-0abf00fb04aa83b480d502ca019900d1.exploit-server.net/
```

{% endcode %}


---

# 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/dom/dom-based-open-redirection.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.
