Content hijacking via stored chat style injection
Published Sep 23, 2022 · Updated May 22, 2025
Stored cross-site scripting in Rocket.Chat before 5.0 allows remote authenticated users to hijack displayed chat content via messages. The complete chat window renders attacker-supplied style content from stored messages without sufficient neutralization, allowing CSS to manipulate the interface and block controls. A target must view the stored message; the reported impact is confined to the viewed interface and its content, with no server-side code execution reported.
Summary
What happened
Stored cross-site scripting in Rocket.Chat before 5.0 allows remote authenticated users to hijack displayed chat content via messages. The complete chat window renders attacker-supplied style content from stored messages without sufficient neutralization, allowing CSS to manipulate the interface and block controls. A target must view the stored message; the reported impact is confined to the viewed interface and its content, with no server-side code execution reported.
The record
- CVE
- CVE-2022-35251
- Published
- Sep 23, 2022
- Updated
- May 22, 2025
- Vendor
- Rocket.Chat Technologies Corp.
- Product
- Rocket.Chat
- Classifications
- CWE-79
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 23, 2022CVE publishedPublication date reported by the CVE source.
- May 22, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Fixed in 5.0>
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- HackerOne report 1401268 proof of conceptproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo