# CVE-2022-35251: Cross-site scripting in Rocket.chat

> Attackers can inject persistent scripts into Rocket.Chat messages to hijack user content and block functionality.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 23 Sep 2022
- **Updated:** 22 May 2025
- **Also known as:** GHSA-72rp-xxph-m42m

## What is CVE-2022-35251?

CVE-2022-35251 is a medium-severity cross-site scripting vulnerability in Rocket.chat Rocket.chat, published on 23 Sep 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A cross-site scripting vulnerability exists in Rocket.chat <v5 due to style injection in the complete chat window, an adversary is able to manipulate not only the style of it, but will also be able to block functionality as well as hijacking the content of targeted users. Hence the payloads are stored in messages, it is a persistent attack vector, which will trigger as soon as the message gets viewed.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2022-35251?

It affects 1 product.


Products: Rocket.chat Rocket.chat.

## How do I fix CVE-2022-35251?

No fix has been published for CVE-2022-35251 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-35251 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-35251 exists.

## Other vulnerabilities in Rocket.chat Rocket.chat

- [CVE-2026-58066](https://insights.sbomify.com/CVE-2026-58066/): Auth bypass in Rocket.Chat (critical 9.8)
- [CVE-2026-29198](https://insights.sbomify.com/CVE-2026-29198/): SQL injection in Rocket.Chat (critical 9.8)
- [CVE-2023-28316](https://insights.sbomify.com/CVE-2023-28316/): Security feature bypass in Rocket.Chat (critical 9.8)
- [CVE-2022-44567](https://insights.sbomify.com/CVE-2022-44567/): Command injection in Rocket.chat - Electron Desktop (critical 9.8)
- [CVE-2021-22910](https://insights.sbomify.com/CVE-2021-22910/): Code injection in Rocket.Chat server (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-35251 and fix it if it is affected.

What it is: CVE-2022-35251 is a medium-severity cross-site scripting vulnerability in Rocket.chat Rocket.chat, published on 23 Sep 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-35251 exists.

Affected product: Rocket.chat Rocket.chat. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-35251/ (Markdown: https://insights.sbomify.com/CVE-2022-35251/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-35251
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-35251
- OSV: https://osv.dev/vulnerability/CVE-2022-35251

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-35251/
Summaries are generated and may contain mistakes; the official description above is the record.