Draft
Sanitize plugin transform HTML by default and document trusted opt-out#24
Conversation
Copilot
AI
changed the title
[WIP] Document and mitigate XSS risk from plugin innerHTML output
Sanitize plugin transform HTML by default and document trusted opt-out
Jul 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Plugin
transform()results were written directly toinnerHTML, creating an XSS path when plugin output included untrusted HTML. This change makes plugin HTML sanitization the default behavior and documents the explicit opt-out for trusted renderers.API
sanitize?: booleantoEzyTablesOptionssanitizetotruesanitize: falsefor trusted plugin outputPlugin HTML handling
transform()output before assigning it toinnerHTMLscript,iframe,object,embed,link,meta,style, andbaseDocumentation
sanitizeoption and when to disable itCoverage
sanitize: falsepath