> For the complete documentation index, see [llms.txt](https://docs.sec1.io/user-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sec1.io/user-docs/4-sast/3-javascript/missing-escape-of-html-entities-in-handlebars-template-compilation.md).

# Missing escape of HTML entities in Handlebars template compilation

## Overview

* **Rule ID**: `javascript_lang_handlebars_no_escape`
* **Applicable Languages**: Javascript
* **Weakness ID**: CWE-80

## Description

In Handlebars (a templating engine for generating HTML markup), setting `noEscape` to true prevents HTML entities from being escaped in the output. This can create a security vulnerability, especially increasing the risk of Cross-Site Scripting (XSS) attacks if the content is sourced from untrusted inputs.

## Remediation Guidelines

* **Do** set noEscape to false when compiling Handlebars templates to ensure HTML entities are properly escaped, thereby reducing the risk of XSS vulnerabilities.

  ```java
  Handlebars.compile(template, { noEscape: false });

  ```

## References

* [**Handlebars compile docs**](https://handlebarsjs.com/api-reference/compilation.html#handlebars-compile-template-options)
* [**OWASP XSS Prevention Cheat Sheet**](https://cheatsheetseries.owasp.org/cheatsheets/Cross_Site_Scripting_Prevention_Cheat_Sheet.html)
* [**CWE-80: Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS)**](https://cwe.mitre.org/data/definitions/80.html)
* [**OWASP Top 10: A03:2021 - Injection**](https://owasp.org/Top10/A03_2021-Injection/)

## Configuration

To omit this rule during a scan, and to provide you with continuous 24/7 code-level scanning, you can employ our [**SAST TOOL**](https://scopy.sec1.io/login)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sec1.io/user-docs/4-sast/3-javascript/missing-escape-of-html-entities-in-handlebars-template-compilation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.