GHSA-xw65-4hp5-5hc7: XSS
Summary
Handlebars.precompile() generates JavaScript source that is commonly embedded in browser <script> elements. Before the fix, static template text containing </script> was emitted unchanged. HTML parsers recognize </script> even inside a JavaScript string literal, closing the surrounding script element and allowing following attacker-controlled markup to be parsed and executed.
This affects applications that precompile attacker-controlled templates and embed the generated source directly in an HTML <script> element. It does not affect ordinary server-side rendering or precompiled templates delivered as external JavaScript files.
Details
Static text is serialized by quotedString() in lib/handlebars/compiler/code-gen.js. The generated JavaScript is valid, but JavaScript quoting alone does not make it safe to embed in HTML. In HTML script data, the sequence </script> terminates the element regardless of JavaScript string context.
On affected releases, this template:
handlebars safe</script><script>alert("XSS")</script><script>
could produce generated source containing:
js return 'safe</script><script>alert("XSS")</script><script>';
When included inline in an HTML document, the first </script> closes the script containing the precompiled template. The next <script> element is then parsed as HTML and executes.
Proof of Concept
js const Handlebars = require('handlebars');
const template = 'safe</script><script>alert("XSS")</script><script>'; const output = Handlebars.precompile(template);
console.log(output.includes('</script>'));
Affected versions print true. Embedding output directly in an inline <script> element allows the injected script tag to be parsed by the browser.
Workarounds
- Do not inline precompiled output from untrusted templates into HTML documents. - Serve generated precompiled templates as external JavaScript files where practical.
Credits
Reported by Curly-Haired-Baboon Aka Laplas
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/handlebarsto a version that resolves this vulnerability.Fixed in 4.7.10 - Compensating control
Do not inline precompiled output from untrusted templates into HTML documents.
- Compensating control
Serve generated precompiled templates as external JavaScript files where practical.
Event History
Frequently Asked Questions
Which deployments are exposed to this issue?
Applications are exposed when they precompile attacker-controlled Handlebars templates and embed the generated JavaScript source directly inside an HTML <script> element. Ordinary server-side rendering and precompiled templates served as external JavaScript files are not affected.
What must an attacker be able to do to exploit it?
An attacker must be able to influence the contents of a template that the application precompiles. The resulting generated source must then be placed directly into an HTML script element, where a </script> sequence in static template text can terminate the element.
How can I determine whether my application is affected?
Review template compilation and delivery paths for use of Handlebars.precompile() on untrusted template content. Affected paths embed the returned source inline in HTML; paths that render on the server or load precompiled output as an external JavaScript file are not affected.
What can be done if an update cannot be applied immediately?
Avoid precompiling attacker-controlled templates into inline script elements. Use server-side rendering or deliver precompiled templates as external JavaScript files instead.