Potential fix for code scanning alert no. 8: Client-side cross-site scripting #1
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/octodemo/jj-vulnerable-node/security/code-scanning/8
To fix the issue, the user-provided input (
in_query
) must be properly escaped before being rendered into the HTML. This can be achieved by replacing<%- in_query %>
with<%= in_query %>
in the EJS template. The<%= %>
syntax escapes the content, ensuring that any special characters in the input are rendered as plain text rather than executable HTML or JavaScript.Additionally, it is good practice to validate or sanitize the input at the source (in
routes/products.js
) to ensure that only expected and safe data is processed.Suggested fixes powered by Copilot Autofix. Review carefully before merging.