BUGFIX: Prevent XSS attacks by coverting special characters to HTML#99
Merged
bwaidelich merged 1 commit intoneos:mainfrom Jan 9, 2026
Merged
Conversation
jonnitto
approved these changes
Oct 29, 2025
Member
|
I can confirm that this fixes the issue, we should issue a bugfix release soon! |
Contributor
|
Thank you @mikec655 for this PR. |
This was referenced Jan 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.
When a Fusion form is submitted with a field that uses, for example, a regex validator, the value is included in the error message when it does not match the pattern:
The given subject did not match the pattern. Got: {value}If the submitted value contains valid HTML, the HTML is rendered instead of displayed as text in the error message. This introduces a potential XSS vulnerability.
To prevent this, I added
String.htmlSpecialChars(...), which ensures that the value is properly escaped and displayed as expected in the error message.