[FIX] Improved security for import output to protect against XSS #93
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.
In this commit, I've addressed a security concern related to the redirect import feature. Specifically, I've taken measures to eliminate a reflected cross-site scripting (XSS) vulnerability in the "import protocol" output.
In simple terms, I've added String.htmlSpecialChrars() to ensure that any user-generated data is now thoroughly encoded. This significantly minimizes the risk of malicious scripts being executed through the output.
If you have any questions about this commit or want more information about the changes, feel free to reach out to me. Your feedback and suggestions are always appreciated!