> 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/xss/dom-xss-with-innerhtml-and-location-search.md).
# DOM XSS with innerHTML and location.search
DOM XSS with innerHTML and location.search notes for PortSwigger Web Security Academy labs, including exploitation workflow, payload testing, Burp Suite validation, and remediation context.
### DOM XSS in InnerHTML Sink Using Source location.search
DOM XSS Vulnerability in the blog search feature. The code recovers the value of `location.search` and inserts directly into the DOM via `innerHTML`, allowing JavaScript to be injected and run when the value comes from the URL.
**Extract from code observed**
```javascript
function doSearchQuery(query) {
document.getElementById('searchMessage').innerHTML = query;
}
var query = (new URLSearchParams(window.location.search)).get('search');
if(query) {
doSearchQuery(query);
}
```
**Payloads tested**
* Simple payload (not interpreted): / ``
* Test to insert an image element:/ ``/ (this does not trigger script execution since no event attribute is present)
Force loading error to trigger a `onerror` handler:/ `` / (This payload uses the `onerror` event attribute to run `alert` when image loading fails)
```javascript
```
The script directly affects `innerHTML` with the `search` value of the URL; Therefore, HTML fragments containing event handlers (e.g. `onerror`) or executable tags may lead to code execution. The `` payload causes a loading error and runs `alert("XSS")`, demonstrating the DOM XSS vulnerability.
---
# 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/xss/dom-xss-with-innerhtml-and-location-search.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.
