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

# Redirección abierta basada en DOM

Notas de Redirección abierta basada en DOM para laboratorios de PortSwigger Web Security Academy, incluido el flujo de explotación, pruebas de payloads, validación con Burp Suite y contexto de remediación.

### Redirección abierta basada en DOM

Este laboratorio contiene una vulnerabilidad de redirección abierta en el lado del DOM. El objetivo es explotar esta vulnerabilidad para redirigir a la víctima al servidor de explotación.

**Fragmento vulnerable (botón "volver al blog")**/ El código de acción asociado con el botón en la sección de comentarios es:

{% code overflow="wrap" %}

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

{% endcode %}

<figure><img src="https://754079710-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>

Este script extrae un `URL` parámetro de la URL actual usando una expresión regular y redirige a su valor si existe; de lo contrario, vuelve a la raíz (`/`).

**Principio de funcionamiento**/ Simplemente añade `&URL=<target>` a la URL de la publicación. Cuando el usuario hace clic en "volver al blog", el script recupera este parámetro y el navegador es redirigido al destino proporcionado.

**Ejemplos de URL**

{% code overflow="wrap" %}

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

{% endcode %}

* — tras cargarla, hacer clic en volver al blog redirige a `https://jord4n.pro`.

<figure><img src="https://754079710-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>

Para el laboratorio (directamente al servidor de explotación):

{% 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/es/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.
