GHSA-7grm-h62g-5m97
MEDIUMNiceGUI is vulnerable to XSS via Unescaped URL in ui.navigate.history.push() / replace()
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.
Blast Radius
niceguiReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
Summary
XSS risk exists in NiceGUI when developers pass attacker-controlled strings into ui.navigate.history.push() or ui.navigate.history.replace(). These helpers are documented as History API wrappers for updating the browser URL without page reload. However, if the URL argument is embedded into generated JavaScript without proper escaping, a crafted payload can break out of the intended string context and execute arbitrary JavaScript in the victim’s browser.
Applications that do not pass untrusted input into ui.navigate.history.push/replace are not affected.
Details
NiceGUI provides ui.navigate.history.push(url) and ui.navigate.history.replace(url) to update the URL using the browser History API. If an application forwards user-controlled data (e.g., URL path segments, query parameters like next=..., form values, etc.) into these methods, an attacker can inject characters such as quotes and statement terminators to escape the JavaScript string context and execute arbitrary code.
A vulnerable pattern is:
- attacker controls a value (e.g., via the request path),
- the application passes it to
ui.navigate.history.push(payload)(orreplace).
This is similar in spirit to other NiceGUI XSS advisories:
ui.html(),ui.chat_message()can cause XSS when developers render untrusted input as HTML (XSS risk/footgun).ui.interactive_imagehad XSS via unsanitized SVG content and was handled as a security advisory with a fix and severity rating.
Because ui.navigate.history.* is expected to accept a URL (data) rather than executable code, the library should escape/encode the argument before emitting JavaScript.
PoC
Create a simple app
from nicegui import ui
@ui.page('/')
def index():
# A link/button a victim could click (attacker can also send the URL directly)
ui.button('open crafted path', on_click=lambda: ui.navigate.to('/%22);alert(document.domain);//'))
@ui.page('/{payload:path}')
def victim(payload: str):
ui.label(f'payload = {payload!r}')
# Vulnerable use: forwarding attacker-controlled path to history.push
ui.button('trigger', on_click=lambda: ui.navigate.history.push(payload))
ui.run()
Run the app
python app.py
Trigger
- Open
http://localhost:8080/ - Click
open crafted path - Click
trigger
Expected result: JavaScript executes (an alert showing document.domain).
Impact
- Vulnerability type: DOM-based XSS
- Attack vector: attacker-controlled input embedded into JavaScript via
ui.navigate.history.push/replace - Affected users: any NiceGUI-based application that forwards untrusted input into
ui.navigate.history.push()orui.navigate.history.replace() - Potential outcomes: client-side code execution, phishing UI injection, and other typical XSS impacts
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | nicegui | ≥ 2.13.0&&< 3.5.0 | 3.5.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for nicegui. 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 nicegui to 3.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7grm-h62g-5m97 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-7grm-h62g-5m97 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-7grm-h62g-5m97. 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-7grm-h62g-5m97 in your dependencies?
O3 detects GHSA-7grm-h62g-5m97 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.