We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
One for the backlog :)
Describe the bug It is possible to run JavaScript on all clients by using the chat option.
To Reproduce Steps to reproduce the behavior:
<script>alert('Hello World!')</script>
Expected behavior The text message should appear (literally) in the chat log, instead of being interpreted by the browser as code.
The text was updated successfully, but these errors were encountered:
Cool! I'll be honest, XSS vulnerabilities haven't been top of my priority list; though that really ought to be fixed.
Sorry, something went wrong.
#14 XSS vulnerability using chat secured
31eed27
31eed27 should close that.
@cdot I figured it was not top priority, hence why I was just adding it to the "backlog" (I really just tried it out of curiosity).
Thanks for the fix!
No branches or pull requests
One for the backlog :)
Describe the bug
It is possible to run JavaScript on all clients by using the chat option.
To Reproduce
Steps to reproduce the behavior:
<script>alert('Hello World!')</script>
as a chat message.Expected behavior
The text message should appear (literally) in the chat log, instead of being interpreted by the browser as code.
The text was updated successfully, but these errors were encountered: