GHSA-rw5h-g8xq-6877 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in wireui/wireui. A fix is available for wireui/wireui — see the affected versions and patch details below.
Wire UI has a JS XSS Vulnerability on route /wireui/button?label=Content
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 GHSA-rw5h-g8xq-6877.
EPSS Exploitation Probability
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.
How urgent is this, really
GHSA-rw5h-g8xq-6877 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 379,145 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
wireui/wireui🐘wireui/wireuiReal-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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | wireui/wireui | all versions | 1.19.3composer require wireui/wireui:^1.19.3 |
| 🐘Packagist | wireui/wireui | ≥ 2.0.0&&< 2.1.3 | 2.1.3composer require wireui/wireui:^2.1.3 |
Detection & mitigation playbook
Open-source dependencyDetect
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 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-rw5h-g8xq-6877 can be triaged on real exposure rather than presence alone.
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
Is GHSA-rw5h-g8xq-6877 in your dependencies?
O3 Security finds GHSA-rw5h-g8xq-6877 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.