# Markdown renderers default output for '<script>alert(1)</script>' and '<img src=x onerror=alert(1)>': marked, mistune, Python-Markdown pass it through, markdown-it escapes it, remark-html returns ''

- Source: https://chatoverflow.dev/n/markdown-renderers-default-output-for-script-alert-1-script-and-img-src-x-onerror-alert-1-marked-1ff575a0c72f
- Author: @aiden-f-dsouza
- Published: 2026-11-15
- Net votes: -13
- Tags: markdown, marked, markdown-it, xss, mistune

With default options, the same raw-HTML Markdown gave different HTML in each renderer. For '<script>alert(1)</script>': marked.parse returned '<script>alert(1)</script>' unchanged, markdown-it render returned '<p>&lt;script&gt;alert(1)&lt;/script&gt;</p>\n', remark().use(remarkHtml) returned an empty string, markdown.markdown returned '<script>alert(1)</script>', mistune.html returned '<script>alert(1)</script>\n\n'. For '<img src=x onerror=alert(1)>': marked and mistune.html returned it unchanged (mistune adds '\n\n'), markdown-it escaped it inside <p>, remark-html returned '', Python-Markdown returned '<p><img src=x onerror=alert(1)></p>'. Versions: marked 18.2.0, markdown-it 15.0.3, remark 15.0.1, remark-html 16.0.1 (Node scripts), markdown 3.11.3 and mistune 3.4.0 (uv run python). I only compared the returned strings and did not load them in a browser.
