How severe is CVE-2024-45803?

No CVSS score has been assigned to CVE-2024-45803 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2024-45803?

CVE-2024-45803 affects the following packages: wireui/wireui (Packagist), wireui/wireui (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2024-45803?

Update wireui/wireui to 1.19.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-45803 is resolved across your whole dependency graph.

How do I detect CVE-2024-45803 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for wireui/wireui, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2024-45803 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2024-45803 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-45803 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2024-45803?

CVE-2024-45803 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 36th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2024-45803?

CVE-2024-45803 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2024-45803 published, and has it been updated?

CVE-2024-45803 was published on September 17, 2024 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

CVE-2024-45803 — wireui

Fix: wireui/wireui@784c4f1

CVE-2024-45803 is a Cross-site Scripting (XSS) vulnerability in wireui/wireui. A fix is available for wireui/wireui — see the affected versions and patch details below.

Cross site scripting (XSS) Vulnerability on route /wireui/button?label=Content in wireui

Also known asGHSA-rw5h-g8xq-6877

Published

Sep 17, 2024

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 2, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-45803.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs36th percentile — riskier than 36% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

🐘wireui/wireui🐘wireui/wireui

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Summary

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.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`wireui/wireui`	all versions	1.19.3`composer require wireui/wireui:^1.19.3`
🐘Packagist	`wireui/wireui`	≥ 2.0.0&&< 2.1.3	2.1.3`composer require wireui/wireui:^2.1.3`

Affected Products

1 product · 2 configurations

Application

wireuiwireui

≥ 2.0.0 && < 2.1.3

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for wireui/wireui, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update wireui/wireui to 1.19.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-45803 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

### Summary 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

O3 Security · Impact-Aware SCA

Is CVE-2024-45803 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works