Snyk has created this PR to upgrade dompurify from 2.4.5 to 2.5.2.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
- The recommended version is **7 versions** ahead of your current version.
- The recommended version was released on **a month ago**.
#### Issues fixed by the recommended upgrade:
| | Issue | Score | Exploit Maturity |
:-------------------------:|:-------------------------|:-------------------------|:-------------------------
![medium severity](https://res.cloudinary.com/snyk/image/upload/w_20,h_20/v1561977819/icon/m.png 'medium severity') | Template Injection [SNYK-JS-DOMPURIFY-6474511](https://snyk.io/vuln/SNYK-JS-DOMPURIFY-6474511) | **586** | Proof of Concept
Release notes Package name: dompurify
Fixed an mXSS sanitizer bypass reported by @ icesfont
Added new code to track element nesting depth
Added new code to enforce a maximum nesting depth of 255
Added coverage tests and necessary clobbering protections
Note that this is a security release and should be upgraded to immediately. Please also note that further releases may follow as the underlying vulnerability is apparently new and further variations may be discovered.
Added new setting SAFE_FOR_XML to enable better control over comment scrubbing
Updated the LICENSE file to show the accurate year number
Updated several build and test dependencies
2.4.9 - 2024-03-21
2.4.8 - 2024-03-19
2.4.7 - 2023-07-11
2.4.6 - 2023-07-10
2.4.5 - 2023-03-01
from dompurify GitHub release notes
---
> [!IMPORTANT]
>
> - Check the changes in this PR to ensure they won't cause issues with your project.
> - This PR was automatically created by Snyk using the credentials of a real user.
> - Max score is 1000. Note that the real score may have changed since the PR was raised.
---
**Note:** _You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs._
**For more information:**
> - š§ [View latest project report](https://app.snyk.io/org/klantinteractie-servicesysteem/project/5208dc30-2f31-46e9-9126-03cc6e8b7ca8?utm_source=github&utm_medium=referral&page=upgrade-pr)
> - š [Customise PR templates](https://docs.snyk.io/scan-using-snyk/pull-requests/snyk-fix-pull-or-merge-requests/customize-pr-templates)
> - š [Adjust upgrade PR settings](https://app.snyk.io/org/klantinteractie-servicesysteem/project/5208dc30-2f31-46e9-9126-03cc6e8b7ca8/settings/integration?utm_source=github&utm_medium=referral&page=upgrade-pr)
> - š [Ignore this dependency or unsubscribe from future upgrade PRs](https://app.snyk.io/org/klantinteractie-servicesysteem/project/5208dc30-2f31-46e9-9126-03cc6e8b7ca8/settings/integration?pkg=dompurify&utm_source=github&utm_medium=referral&page=upgrade-pr#auto-dep-upgrades)
This PR was automatically created by Snyk using the credentials of a real user.
![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)
Snyk has created this PR to upgrade dompurify from 2.4.5 to 2.5.2.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.- The recommended version is **7 versions** ahead of your current version. - The recommended version was released on **a month ago**. #### Issues fixed by the recommended upgrade: | | Issue | Score | Exploit Maturity | :-------------------------:|:-------------------------|:-------------------------|:------------------------- ![medium severity](https://res.cloudinary.com/snyk/image/upload/w_20,h_20/v1561977819/icon/m.png 'medium severity') | Template Injection
[SNYK-JS-DOMPURIFY-6474511](https://snyk.io/vuln/SNYK-JS-DOMPURIFY-6474511) | **586** | Proof of Concept
Release notes
Package name: dompurify
Note that this is a security release and should be upgraded to immediately. Please also note that further releases may follow as the underlying vulnerability is apparently new and further variations may be discovered.
SAFE_FOR_XML
to enable better control over comment scrubbing