~ / search / GHSA-98hj-9722-w3j8

GHSA-98hj-9722-w3j8

Astro: Reflected/Stored XSS via unescaped <script>/<style> tag content in JSX/MDX rendering

Source: GitHub Advisory Database (reviewed) Moderate CVE-2026-114128

Packages

EcosystemPackageAffectedFixed in
npm astro < 7.3.2 7.3.2

Details

As written in the advisory (Markdown source, shown as plain text).

## Summary Astro's JSX and MDX rendering pipeline treated string children of `<script>` and `<style>` elements as trusted HTML. When a dynamic value was passed through a JSX expression, such as `<script>{value}</script>`, an attacker-controlled value containing `</script>` or `</style>` could terminate the element and inject arbitrary HTML and JavaScript. Other JSX expression contexts escaped dynamic strings automatically. This behavior was limited to `<script>` and `<style>` children rendered through Astro's `astro:jsx` renderer, including MDX components. ## Details The affected rendering paths marked all string children of `<script>` and `<style>` elements as safe HTML, without distinguishing literal content generated by the compiler from dynamic expression values. An application was vulnerable when attacker-controlled data, such as a query parameter or CMS field, was interpolated directly into one of these elements. For example, a value containing `</script><script>alert(1)</script>` passed to `<script>{value}</script>` was emitted without escaping. The browser interpreted the first closing tag as markup and executed the injected script. The fix preserves raw rendering for literal script and style content while escaping dynamic string children like other JSX expression values. ## Impact Affected applications could be vulnerable to reflected or stored cross-site scripting. Exploitation required an application to pass attacker-controlled data directly as a dynamic child of a `<script>` or `<style>` element in MDX or through the `astro:jsx` runtime. Successful exploitation allowed arbitrary JavaScript execution in the victim's browser under the application's origin. ## Patches This issue is patched in `[email protected]`. ## Workarounds Do not interpolate untrusted dynamic values directly into `<script>` or `<style>` element children. Applications that cannot upgrade should validate and contextually encode these values before rendering them. ## Credit Reported by [@RKasai127](https://github.com/RKasai127).

References

External links from the advisory. They lead to third-party sites.