[Snyk] Security upgrade dompurify from 3.3.0 to 3.4.0

[heather-formio]

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• package.json

⚠️ Warning

Failed to update the package-lock.json, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Operator Precedence Logic Error SNYK-JS-DOMPURIFY-16078387	601

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[heather-formio]

This is a minor version upgrade for dompurify from 3.3.0 to 3.4.0. The release consists primarily of security fixes and bug fixes related to sanitization logic.

Key Changes:

• Behavioral Fixes: The update addresses several edge cases where configuration options could be bypassed or lead to unexpected behavior. For example, a fix ensures FORBID_TAGS now correctly overrides ADD_TAGS.
• Security Patches: The release includes fixes for several potential mutation XSS (mXSS) vulnerabilities and prototype pollution issues.

While this release does not introduce explicitly breaking API changes, the fixes alter sanitization behavior to be more strict and correct. This could potentially affect applications that were unintentionally relying on the previous, less strict behavior.

Recommendation: This upgrade is recommended for its security enhancements. However, due to the behavioral changes in sanitization, it is important to verify that the stricter parsing does not negatively impact legitimate use cases in your application.

Source: GitHub Release Notes

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.