`), it is possible to inject arbitrary HTML into the transformed output by supplying a malicious URL query string to `server.transformIndexHtml`. Only apps using `appType: 'custom'` and using the default Vite HTML middleware are affected. The HTML entry must also contain an inline script. The attack requires a user to click on a malicious URL while running the dev server. Restricted files aren't exposed to the attacker. This issue has been addressed in vite@5.0.5, vite@4.5.1, and vite@4.4.12. There are no known workarounds for this vulnerability.", "datePublished": "2023-12-04T23:03:30Z", "dateModified": "2025-05-29T13:40:53Z", "keywords": "CVE-2023-49293, vulnerability, CVE, security, vite, vitejs", "about": { "@type": "SoftwareApplication", "name": "vite", "applicationCategory": "SecurityApplication", "operatingSystem": "All" } }
CVE-2023-49293 MEDIUM

CVE-2023-49293: Cross-site Scripting in `server.transformIndexHtml` via URL payload in vite

Vendor Vitejs
Product vite
Weakness CWE-79 · XSS
Published December 4, 2023
Last update May 29, 2025

CVSS base score

6.1/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction Required
Confidentiality Low
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

What the vulnerability does

01Description

Vite is a website frontend framework. When Vite's HTML transformation is invoked manually via `server.transformIndexHtml`, the original request URL is passed in unmodified, and the `html` being transformed contains inline module scripts (`<script type="module">...</script>`), it is possible to inject arbitrary HTML into the transformed output by supplying a malicious URL query string to `server.transformIndexHtml`. Only apps using `appType: 'custom'` and using the default Vite HTML middleware are affected. The HTML entry must also contain an inline script. The attack requires a user to click on a malicious URL while running the dev server. Restricted files aren't exposed to the attacker. This issue has been addressed in vite@5.0.5, vite@4.5.1, and vite@4.4.12. There are no known workarounds for this vulnerability.

Key dates

02Disclosure timeline

December 4, 2023 CVE published
May 29, 2025 Record updated