telegram-search Stored XSS via v-html in MessageList.vue
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| GramSearch | telegram-search | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Gramsearch | Telegram-search |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.662% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Gramsearch
Gramsearch telegram-search |
|
| Vendors & Products |
Gramsearch
Gramsearch telegram-search |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | telegram-search contains a stored cross-site scripting vulnerability that allows remote attackers to execute arbitrary JavaScript in victims' browsers by sending crafted messages containing unsanitized HTML to a shared Telegram group. The highlightKeyword function in MessageList.vue passes raw message content directly to v-html without HTML escaping or sanitization, enabling stored, cross-user, zero-click execution of injected payloads such as image onerror handlers when victims browse or search messages. | |
| Title | telegram-search Stored XSS via v-html in MessageList.vue | |
| Weaknesses | CWE-79 | |
| References |
|
|
| Metrics |
cvssV3_1
|