S4E just found a high-severity finding from top 10 tcp port service scan
PlatformPlansPartners
Resources
ToolsBlogDocs
Sign Up →
medium·Product Based Web Vulnerabilities·Updated Apr 1, 2026

CVE-2023-49293 Scanner

CVE-2023-49293 Scanner - Cross-Site Scripting (XSS) vulnerability in Vite dev server

Est. Time~10 seconds
Scan TypeSingle Scan
Targetsurl
CostFree
3.3k
Times Used
continuous scan runs
4.7k
Continuously Checked
assets under CS
0
Vulnerabilities Found
confirmed findings
References
CVECVE-2023-49293
6.1
CVSSmedium
Exploitable remotely over the internet · no authentication required · user interaction needed.

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 [email protected], [email protected], and [email protected]. There are no known workarounds for this vulnerability.

Attack Vector
Network
Privileges Req.
None
User Interaction
Required
Affected
viteby vitejs
>=4.4.0, < 4.4.12
Updated Aug 22, 2026View on NVD →
Detail

Vite dev server is widely used by developers around the world as a tool for building and serving web applications. It is primarily used by frontend developers who are working with projects using modern JavaScript frameworks like Vue.js, React, or Angular. The dev server provides fast and efficient service, allowing for a smooth development experience with hot module replacement and other useful features. It is used in development environments to quickly see changes in code reflected in the browser. Being open-source, it is favored for its flexibility and ease of customization to fit various development needs. Vite's popularity in the developer community is due to its performance enhancements over traditional build tools.

A Cross-Site Scripting (XSS) vulnerability allows attackers to inject malicious scripts into web pages viewed by other users. This particular vulnerability exists in Vite's dev server when configured with `appType: 'custom'`. The vulnerability is primarily due to improperly sanitizing URL requests that are manually invoked using `server.transformIndexHtml`. When exploited, an attacker can craft a URL that injects malicious scripts. This vulnerability exposes users to potential data theft, session hijacking, or other unauthorized actions executed via the injected scripts. It is critical that configurations follow secure practices to prevent such vulnerabilities.

The specific XSS vulnerability affects Vite dev server configurations that manually execute `server.transformIndexHtml` with unmodified request URLs. The vulnerability allows injected scripts via the URL, which can execute in the browser context if an inline module script exists in the HTML being served. Attackers exploiting this could craft specially constructed URLs that perform malicious actions. Typical payloads might involve JavaScript alert executions or more harmful scripts accessing sensitive browsing data. Developers must be aware of secure coding practices and avoid exposing such endpoints to potential manipulation.

If exploited, this vulnerability could lead to a range of harmful effects such as unauthorized access to user sessions, theft of sensitive browser data, including cookies and session tokens, and injection of further harmful scripts. It undermines the security posture by making client-side attacks feasible. Developers relying on vulnerable versions may inadvertently expose their test or development environments to exploitation. Though typically a low-risk environment, the implications for sensitive data exposure or application abuse still pose significant security concerns.

REFERENCES

Solution Advice
  • Update Vite dev server to the latest patched version: v5.0.5, v4.5.1, or v4.4.12.
  • Ensure proper validation and sanitization of all URL inputs within the development configuration.
  • Regularly audit and monitor server configurations to detect potential weaknesses.
  • Utilize HTTP headers like Content Security Policy (CSP) to mitigate the impact of script injections.
  • Train development teams on secure coding practices to prevent introduction of similar vulnerabilities.

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

11,000+ scanners. Free to start. No credit card required.