Potential fix for code scanning alert no. 5: DOM text reinterpreted as HTML#32
Merged
Potential fix for code scanning alert no. 5: DOM text reinterpreted as HTML#32
Conversation
…s HTML Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Contributor
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
tdn-client | 775fd0f | Commit Preview URL Branch Preview URL |
Apr 25 2026, 09:37 AM |
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
1 participant
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/the-developer-network/tdn-client/security/code-scanning/5
To fix this safely without changing intended functionality, validate avatar URL values before binding them to
<img src>, and only allow trusted schemes (blob:,http:,https:) or root-relative URLs. If validation fails, fall back to a safe default avatar URL. This should be done inEditProfileModal.tsxwherecurrentAvataris constructed, so the sink always receives a sanitized URL string.Best implementation in shown code:
src/features/profile/components/EditProfileModal.tsx, add a small local helper (e.g.getSafeImageSrc) abovecurrentAvatar.currentAvatar.No dependency changes are required.
Suggested fixes powered by Copilot Autofix. Review carefully before merging.