<img src="dummy.png" onerror="alert()"/>

If you're refering to showdown being vulnerable to XSS attacks, please check the following link: https://github.com/showdownjs/showdown/wiki/Markdown's-XSS-Vulnerability-(and-how-to-mitigate-it)
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鈥檒l break some of Markdown鈥檚 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.
example:
http://demo.showdownjs.com/#!/%3Cimg%20src%3D%22dummy.png%22%20onerror%3D%22alert()%22%2F%3E
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.
Duplicate of: #555 #454 #446 #283 #282 #252 #216 #182 #71 #70 #57
Most helpful comment
If you're refering to showdown being vulnerable to XSS attacks, please check the following link: https://github.com/showdownjs/showdown/wiki/Markdown's-XSS-Vulnerability-(and-how-to-mitigate-it)
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.
example:
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.
Duplicate of: #555 #454 #446 #283 #282 #252 #216 #182 #71 #70 #57