Summary
Wire UI has a JS XSS Vulnerability on route /wireui/button?label=Content
A potential Cross-Site Scripting (XSS) vulnerability has been identified in the /wireui/button endpoint, specifically through the label query parameter. Malicious actors could exploit this vulnerability by injecting JavaScript into the label parameter, leading to the execution of arbitrary code in the victim's browser.
Details
The /wireui/button endpoint dynamically renders button labels based on user-provided input via the label query parameter. Due to insufficient sanitization or escaping of this input, an attacker can inject malicious JavaScript. The following URL demonstrates the vulnerability:
https://wireui.dev/wireui/button?label=Cancel&1%25%7ds8dk0%3E%3Cscript%3Ealert(1)%3C/script%3Ez1qt3=1
By crafting such a request, an attacker can inject arbitrary code that will be executed by the browser when the endpoint is accessed.
Proof of Concept (PoC)
To demonstrate the vulnerability, visit the following URL:
/wireui/button?label=<script>alert(1)</script>
Upon loading the page, the injected JavaScript will execute, displaying an alert with the message "1." This confirms the vulnerability and highlights that user input is not being properly escaped or sanitized.
Impact
If exploited, this vulnerability could allow an attacker to execute arbitrary JavaScript code in the context of the affected website. This could lead to:
- Session Hijacking: Stealing session cookies, tokens, or other sensitive information.
- User Impersonation: Performing unauthorized actions on behalf of authenticated users.
- Phishing: Redirecting users to malicious websites.
- Content Manipulation: Altering the appearance or behavior of the affected page to mislead users or execute further attacks.
The severity of this vulnerability depends on the context of where the affected component is used, but in all cases, it poses a significant risk to user security.
Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.
CVE-2024-45803 has a CVSS score of 6.1 (Medium). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.19.3, 2.1.3); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
wireui/wireui to 1.19.3 or later; wireui/wireui to 2.1.3 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2024-45803? CVE-2024-45803 is a medium-severity cross-site scripting (XSS) vulnerability in wireui/wireui (composer), affecting versions < 1.19.3. It is fixed in 1.19.3, 2.1.3. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
- How severe is CVE-2024-45803? CVE-2024-45803 has a CVSS score of 6.1 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of wireui/wireui are affected by CVE-2024-45803? wireui/wireui (composer) versions < 1.19.3 is affected.
- Is there a fix for CVE-2024-45803? Yes. CVE-2024-45803 is fixed in 1.19.3, 2.1.3. Upgrade to this version or later.
- Is CVE-2024-45803 exploitable, and should I be worried? Whether CVE-2024-45803 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2024-45803 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2024-45803?
- Upgrade
wireui/wireuito 1.19.3 or later - Upgrade
wireui/wireuito 2.1.3 or later
- Upgrade