CVE-2022-23466 is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in teler.app. A fix is available for teler.app — see the affected versions and patch details below.
DOM-based cross-site scripting (XSS) in teler dashboard
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2022-23466.
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
CVE-2022-23466 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 377,636 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
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.4go get teler.app@v2.0.0-rc.4 |
| 🐹Go | teler.app | ≥ 2.0.0-dev&&< 2.0.0-dev.2 | 2.0.0-dev.2go get teler.app@v2.0.0-dev.2 |
| 🐹Go | teler.app | ≥ 0.0.0-20220625162531-2289e90590a9&&< 0.0.0-20221203202318-20f59eda2420 | 0.0.0-20221203202318-20f59eda2420go get teler.app@v0.0.0-20221203202318-20f59eda2420 |
| 🐹Go | teler.app | ≥ 1.2.3-0.20220625162531-2289e90590a9&&< 1.2.3-0.20221203202318-20f59eda2420 | 1.2.3-0.20221203202318-20f59eda2420go get teler.app@v1.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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 CVE-2022-23466 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 CVE-2022-23466 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2022-23466. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2022-23466 in your dependencies?
O3 Security finds CVE-2022-23466 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.