You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Showdown tries to convert the input text as closely as possible, without any concerns for XSS attacks or malicious intent. So, the basic rules are:
removing HTML entities from markdown does not prevent XSS. Markdown syntax can generate XSS attacks.
XSS filtering should be done AFTER Showdown has processed any input, not before or during. If you filter before, it’ll break some of Markdown’s features and will leave security holes.
perform the necessary filtering server-side, not client side. XSS filtering libraries are useful but shouldn't be used blindly.
If you're referring to the Demo page, it's not possible (as far as I know) to use that page to target other people, only yourself. Even if you share a malicious composite link, the input gets sanitized.
Besides, the demo page doesn't store any relevant user information (just the last used options in the website), so an attack would be rather pointless.
The text was updated successfully, but these errors were encountered: