docs: Potential fix for code scanning alert no. 794: DOM text reinterpreted as HTML #8172
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
…preted as HTML Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
✅ Deploy Preview for label-studio-docs-new-theme ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for heartex-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for label-studio-storybook canceled.
|
✅ Deploy Preview for label-studio-playground canceled.
|
huguestennier
changed the title
niklub
approved these changes
Aug 19, 2025
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.
Potential fix for https://github.com/HumanSignal/label-studio/security/code-scanning/794
To fix the issue, we need to ensure that the
namevalue derived fromtab.dataset.nameis properly sanitized or escaped before being used in thebuttonsstring. The best approach is to use a utility function to escape special HTML characters (<,>,&,",') in thenamevalue. This ensures that any potentially malicious input is rendered as plain text rather than being interpreted as HTML.The fix involves:
escapeHTMLto escape special HTML characters.namevalue before appending it to thebuttonsstring.Testing
Tabs component under https://deploy-preview-8172--heartex-docs.netlify.app/guide/export#COCO should work as before