---
sourceDocument: Australia Platform security
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/platform-security

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Disable embedded HTML code \[Updated in Security Center 1.3\]

# Disable embedded HTML code \[Updated in Security Center 1.3\] {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 Minuten Lesedauer

Use the glide.ui.security.allow_codetag property to disable support for embedding HTML code created using the \[code\] tag.
Disable support for displaying HTML code embedded using the `[code]` tag. This tag allows rendered HTML to display in journal fields and may lead to cross-site scripting (XSS) attacks. These attacks can enable
foreign scripts to execute on a user session in the logged in browser's context. Attackers can use these scripts to steal session information and sensitive data. The HTML language was not designed to separate script from formatting,
so allowing user-controlled HTML in any system has inherent risk.

Setting the glide.ui.security.codetag.allow_script to false is compliant, and significantly reduces this risk, however some small risk remains. It disables only the script portion of a
`code` tag, and relies on sanitizing all known conventions of script in the HTML.

Set the glide.ui.security.allow_codetag system property to false to completely prohibit journal fields and forms from displaying rendered HTML.  
The ServiceNow AI Platform mitigates many injection and cross-site attacks by implementing escaping and encoding techniques. As a result, users can't write/submit HTML formatted inputs for journal fields. But journal fields can render text enclosed within code tags as HTML.

* However, there is an associated security risk. If set to <kbd class="ph userinput">true</kbd>, malicious users can write harmful HTML JS code that may be executed on a different client browser after rendering of journal fields.
* Set this property to <kbd class="ph userinput">false</kbd> so that administrators can prevent journal fields from rendering HTML code by disabling support for the `[code]` tag.
{#sc-allow-embedded-html-code__ul_alw_3yq_nkb}

## More information {#sc-allow-embedded-html-code__section_more_information}

{#sc-allow-embedded-html-code__table_ajc_b43_3kb__entry__2}

| Attribute | Description |
|-|-|
| Property name | glide.ui.security.allow_codetag |
| Configuration type | System Properties (/sys_properties_list.do) |
| Category | [Validation, sanitization, and encoding](https://servicenow-prod.fluidtopics.net/F1nREUr0FIKK6cga6jbKwg "Validation, sanitization, and encoding addresses input validation to prevent against vulnerabilities like Cross-Site Scripting (XSS), SQL injection and other attacks.") |
| Configure in Instance Security Center | Yes |
| Purpose | Protect against cross-site scripting and malicious script execution |
| Recommended value | false |
| Default value | true |
| Security risk rating | 4.2 |
| Functional impact | This remediation enforces HTML encoding to occur on the UI and renders the encoded results to the user. This property is set to <kbd class="ph userinput">true</kbd> by default. In this state, your instance displays rendered HTML in journal fields and forms. If this property is set to <kbd class="ph userinput">false</kbd>, HTML is not rendered properly and HTML tags may appear in journal fields on forms. It can have an adverse impact on functionality, and on user interactions with the resulting data. |
| Security risk | (Medium) Input validation must occur in the application to defend against cross-site scripting attacks. These attacks enable foreign scripts to execute on a user session in the logged in browser's context. Attackers can use it to steal session information and sensitive data. |
[ ]

{#sc-allow-embedded-html-code__table_ajc_b43_3kb}