This repository was archived by the owner on Aug 21, 2025. It is now read-only.
Potential fix for code scanning alert no. 16: Reflected cross-site scripting #385
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
…ripting Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
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.
Potential fix for https://github.com/microsoft/AcademicContent/security/code-scanning/16
To fix the reflected XSS vulnerability, we should ensure that any user-provided data is properly sanitized before being stored or returned in API responses. Since the
/api/postsendpoint returns all posts, including those created by users, we should escape any potentially dangerous content before sending it in the response. The best way to do this is to encode/escape all string fields in each post before sending the response. We can use a well-known library such asescape-htmlto escape HTML special characters in string fields. This can be done by mapping over thepostsarray and escaping all string fields in each post before sending the response in the/api/postsGET handler.Required changes:
escape-htmlimport at the top of the file./api/postsGET handler, map over thepostsarray and escape all string fields in each post before sending the response.Suggested fixes powered by Copilot Autofix. Review carefully before merging.