> 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-in-angularjs-with-encoded-angle-brackets-and-quotes.md).
# DOM XSS in AngularJS with Encoded Angle Brackets and Quotes
DOM XSS in AngularJS with Encoded Angle Brackets and Quotes notes for PortSwigger Web Security Academy labs, including exploitation workflow, payload testing, Burp Suite validation, and remediation co
### DOM XSS in AngularJS Expression with Angle Brackets and Double Quotes HTML-encoded
This activity shows an XSS DOM vulnerability in an AngularJS expression used by the search feature. AngularJS analyzes HTML nodes containing the `ng-app` directive and allows you to evaluate expressions inside double brackets `{{ }}` — which can be abused to run JavaScript even when the `<` and `>` angle brackets and quotes are encoded on the HTML side. Lab objective: Inject an AngularJS expression that runs `alert()`.
* Site analysis with Wappalyzer indicates the presence of AngularJS.
* The All The ThingsPayloads resource contains useful payloads for this case (examples provided below).
Payloads tested
```javascript
{{constructor.constructor('alert(1)')()}}
```
```
{{[].pop.constructor('alert/u00281/u0029')()}}
```
---
# 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-in-angularjs-with-encoded-angle-brackets-and-quotes.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.
