[opencode] VULN-117372 Fix SQL injection vulnerability in durable-chat-template#958
Merged
deloreyj merged 1 commit intocloudflare:mainfrom Mar 9, 2026
Merged
Conversation
Contributor
|
Preview link not generated: you must be on a branch, not on a fork. |
deloreyj
approved these changes
Mar 9, 2026
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
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.
Description
Fixes #VULN-117372
Have tested changes with a deployed version of the DO template: https://durable-chat-template.kylieski.workers.dev
Description from OpenCode:
This change fixes a SQL injection vulnerability in the durable-chat-template. The
saveMessagemethod was building SQL queries using string interpolation, which is dangerous because user-provided values (like message.user or message.content) were being inserted directly into the query string.Before:
After:
Using parameterized queries (? placeholders) ensures user input is properly escaped and can never be interpreted as SQL commands.