---
sourceDocument: Brazil Platform security
sourceDocumentLink: https://www.servicenow.com/docs/r/platform-security

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Escape jelly script

# Escape jelly script {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Use the glide.ui.escape_all_script property to force escape of all scripts injected into Jelly.
This property escapes all the JS and HTML strings included in \<j:jelly\> ... \</j:jelly\> before they are written to the output stream, preventing several XSS issues from occurring. If
glide.ui.escape_all_script is not set to the recommended value of true, then escaping of scripts injected into Jelly is disabled. Without this mitigation, the platform becomes widely open to a variety of
script injection attacks. An attacker could execute arbitrary Rhino scripts on the instance.  
Warning:  
Be careful when using these tags. If user input is displayed here it can open a security vulnerability.

## More information {#sc-escape-jelly__section_more_information}

{#sc-escape-jelly__table_ajc_b43_3kb__entry__2}

| Attribute | Description |
|-|-|
| Property name | glide.ui.escape_all_script |
| Configuration type | System Properties (/sys_properties_list.do) |
| Data type | Boolean |
| Category | [Validation, sanitization, and encoding](https://www.servicenow.com/docs/Y54hkYpvZcFtgJ5PMM2JEw "Validation, sanitization, and encoding addresses input validation to prevent against vulnerabilities like Cross-Site Scripting (XSS), SQL injection and other attacks.") |
| Purpose | If the property is not set to true, developers have to perform several steps on each custom Jelly script to prevent XSS issues. These steps include locating the Jelly variables being sent to output stream to render on web pages, and performing escaping on each of the following tags: `$â {JS:expression}` `$â {HTML:expression}` OR `$â {JS,HTML:expression}` |
| Recommended value | true |
| Default value | true |
| Security risk rating | 7.3 |
| Functional impact | This remediation enforces Jelly escaping at the parser level. It can have a functionality impact on user interaction with the resulting data. |
| Security risk | (High) Input validation has to occur on all the user input being entered on the application. By doing so, injection attacks against the platform can be defended and protected. |
| Workaround | The UI may be affected because some of the scripts and HTML tags designed for rendering on a web page may appear broken. This remediation sends the output encoded page to the browser to render. For example, instead of `'my string here'`, it might display '`<u>my string here</u>` as the `<u>` tag was properly escaped. In this case, to prevent escaping, add the NOESC prefix to Jelly expression to prevent JS escaping. For example: * Before: ($\[jvar_context_menus\]); * After: `($[NOESC:jvar_context_menus]);` * Before: $\[jvar_ui_policy_scripts\] * After: `$[NOESC:jvar_ui_policy_scripts]` {#sc-escape-jelly__ul_qmt_b1n_dlb} Warning: Be careful when using these tags. If user input is displayed here it can open a security vulnerability. |
| References | [High Security Settings](https://www.servicenow.com/docs/_g5o20kuRsWDHQZC7ejjuw "High Security Settings refer to several security options available in your instance.") [Jelly tags](https://www.servicenow.com/docs/access?context=r_JellyTags&version=brazil&pubname=brazil-api-reference&ft:locale=en-US) |
[ ]

{#sc-escape-jelly__table_ajc_b43_3kb}

To learn more about adding or creating a system
property, see [Add a system property](https://www.servicenow.com/docs/access?context=t_AddAPropertyUsingSysPropsList&version=brazil&pubname=brazil-platform-administration&ft:locale=en-US).