How severe is GHSA-rw5h-g8xq-6877?

GHSA-rw5h-g8xq-6877 has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-rw5h-g8xq-6877?

GHSA-rw5h-g8xq-6877 affects the following packages: wireui/wireui (Packagist), wireui/wireui (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-rw5h-g8xq-6877?

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

How do I detect GHSA-rw5h-g8xq-6877 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for wireui/wireui. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-rw5h-g8xq-6877 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-rw5h-g8xq-6877?

O3 pinpoints whether GHSA-rw5h-g8xq-6877 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-rw5h-g8xq-6877 actively exploited in the wild?

No public exploit code has been indexed for GHSA-rw5h-g8xq-6877 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 GHSA-rw5h-g8xq-6877?

GHSA-rw5h-g8xq-6877 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 31th 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 GHSA-rw5h-g8xq-6877?

GHSA-rw5h-g8xq-6877 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 GHSA-rw5h-g8xq-6877 published, and has it been updated?

GHSA-rw5h-g8xq-6877 was published on September 17, 2024 and was last updated on September 17, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

GHSA-rw5h-g8xq-6877

MEDIUM

Wire UI has a JS XSS Vulnerability on route /wireui/button?label=Content

Also known asCVE-2024-45803

Published

Sep 17, 2024

Updated

Sep 17, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk31th percentile-0.04%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

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
🐘Packagist	`wireui/wireui`	≥ 2.0.0&&< 2.1.3	2.1.3

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update wireui/wireui to 1.19.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rw5h-g8xq-6877 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-rw5h-g8xq-6877 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-rw5h-g8xq-6877. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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 GHSA-rw5h-g8xq-6877 in your dependencies?

O3 detects GHSA-rw5h-g8xq-6877 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works