This repository has been archived by the owner on Dec 19, 2023. It is now read-only.
Fix for the Cross-site Scripting (XSS) Vulnerability #1
Conversation
This file contains 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
|
Congratulations @mufeedvh - you are the successful huntr! Thank you for submitting your fix - we have approved your pull request and will merge your commits into our master branch. If you have any questions, please respond in the comments section. Your bounty is on its way - keep hunting. |
|
Thank You @JamieSlome ✌️ |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
As a blog post contain images and other elements, we need to allow HTML input but prevent JavaScript code to execute/XSS attacks. So, I used DOMPurify to accept HTML but no JavaScript thus fixing the XSS vulnerability.
Fixed XSS on three endpoints:
Fixed! 👍