# Usage of vulnerable DOMPurify package

## Overview

* **Rule ID**: `javascript_third_parties_dom_purify`
* **Applicable Languages**: Javascript
* **Weakness ID**: CWE-79

## Description

For DOMPurify versions prior to 2.0.17, there are XSS vulnerabilities when using the sanitize function without proper configuration.

## Remediation Guidelines

* **Do** upgrade DOMPurify to version 2.0.17 or greater, and specify a secure configuration option.

  ```javascript
  // either
  DOMPurify.sanitize(htmlToSanitize, { RETURN_DOM_IMPORT:true })
  // or
  DOMPurify.sanitize(htmlToSanitize, { RETURN_DOM_FRAGMENT: true })
  ```

## References

* [**Vulnerability explained**](https://research.securitum.com/mutation-xss-via-mathml-mutation-dompurify-2-0-17-bypass)
* [**CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')**](https://cwe.mitre.org/data/definitions/79.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: 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:

```
GET https://docs.sec1.io/user-docs/4-sast/3-javascript/usage-of-vulnerable-dompurify-package.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.