GHSA-xr7p-8q82-878q
LOWteler dashboard vulnerable to DOM-based cross-site scripting (XSS)
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
teler.app🐹teler.app🐹teler.app🐹teler.appReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Description
teler prior to version <= 2.0.0-rc.4 is vulnerable to DOM-based cross-site scripting (XSS) in the teler dashboard. When teler requests messages from the event stream on the /events endpoint, the log data displayed on the dashboard are not sanitized.
Impact
This only affects authenticated users and can only be exploited based on detected threats if the log contains a DOM scripting payload. This indicates a low severity and there is no significant impact on the users.
Affected Version
This issue was introduced from version v2.0.0-rc to v2.0.0-rc.3 & v2.0.0-dev.
Patches
This vulnerability has been fixed on version v2.0.0-rc.4 & v2.0.0-dev.2.
Workarounds
Here are some workarounds to handle this case:
- Deactivate the live event dashboard from the configuration file, or
- Upgrade teler version to
v2.0.0-rc.4orv2.0.0-dev.2& above.
References
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | teler.app | ≥ 2.0.0-rc&&< 2.0.0-rc.4 | 2.0.0-rc.4 |
| 🐹Go | teler.app | ≥ 2.0.0-dev&&< 2.0.0-dev.2 | 2.0.0-dev.2 |
| 🐹Go | teler.app | ≥ 0.0.0-20220625162531-2289e90590a9&&< 0.0.0-20221203202318-20f59eda2420 | 0.0.0-20221203202318-20f59eda2420 |
| 🐹Go | teler.app | ≥ 1.2.3-0.20220625162531-2289e90590a9&&< 1.2.3-0.20221203202318-20f59eda2420 | 1.2.3-0.20221203202318-20f59eda2420 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for teler.app. 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 teler.app to 2.0.0-rc.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xr7p-8q82-878q 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-xr7p-8q82-878q 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-xr7p-8q82-878q. 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-xr7p-8q82-878q in your dependencies?
O3 detects GHSA-xr7p-8q82-878q across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.