Fix SQL injection in product routes#69
Open
michellesdawg wants to merge 1 commit into
Open
Conversation
Co-authored-by: michellesdawg <171616914+michellesdawg@users.noreply.github.com>
|
I can only run on private repositories. |
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.
For campaign
Batch fix for javascript-node-security/sql-injection Apr. 17 2026created by Michelle Sun • View in Dev Agent CampaignThis PR fixes SQL injection vulnerabilities in the product routes by replacing string concatenation with parameterized queries.
Changes:
?placeholders/search,/by-price, and/category/:catSecurity Impact:
These changes eliminate the risk of SQL injection attacks by ensuring user input is properly escaped and treated as data rather than executable SQL code.
Testing:
The changes maintain the same functionality while improving security. All existing tests should pass as the query logic remains unchanged, only the parameter handling has been updated.
PR by Bits - View session in Datadog
Comment @DataDog to request changes