fix: harden plugin HTML rendering - #18
Merged
Merged
Conversation
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.
Closes the five current high CodeQL findings by replacing permissive script-tag regex parsing, completing generated Markdown escaping, and rendering form-builder markup through an inert explicit DOM allowlist instead of dynamic innerHTML.\n\nVerified: full SDK/plugin unit, integration and Core E2E tests; generated docs and package contents; strict Indexer 18/18; governed revision 66a3504962608e21b94fe6360e5d0188d5e68bcfe06a8a0dde8e4f1e2d7a358c accepted.