> 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/xss-in-template-literal-with-escaped-unicode.md).
# XSS in a Literal Template with Escaped Unicode Characters
XSS in a Literal Template with Escaped Unicode Characters notes for PortSwigger Web Security Academy labs, including exploitation workflow, payload testing, Burp Suite validation, and remediation cont
### Reflected XSS Into a Template Literal with Angle Brackets, Single, Double Quotes, Backslash and Backticks Unicode-escaped
XSS reflected in a literal template (backticks) where `<` and `>` angle brackets as well as single and double quotes are encoded, and the backtick is escaped in Unicode. The objective: cause the execution of `alert()` within the string template.
The search parameter is reflected in a JavaScript literal template. The template string must be broken to run `alert()` from the reflected value.
var message = `2 search results for 'test'`;
document.getElementById('searchMessage').innerText = message;
* The backtick character (`` ` ``) delimits the template literal; the page escapes the user-supplied backtick (for example, using Unicode escaping), preventing a simple breakout.
Example of JS interpolation difference (illustration):
```javascript
variable = "Testing";
console.log("The variable is: ${variable}")
console.log(`The variable is: ${variable}`)
```
The first line literally displays `${variable}`, the second interprets the variable with backticks.
* Trying to insert an interpolation expression that runs `alert()`:
```javascript
${alert(0)}
```
---
# 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/xss-in-template-literal-with-escaped-unicode.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.
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)