Security readout for executives and security teams
Plain-English summary
Rocket.Chat versions before v5 can store malicious style content in chat messages. When a targeted user views the message, the attacker may alter the chat window, block functions, or manipulate displayed content. This is not rated critical, but persistent user-facing compromise makes it relevant for support, community, and customer chat environments.
Executive priority
Treat this as a moderate-priority remediation item, higher if Rocket.Chat supports customer-facing or public communities. The main business risk is trust and targeted user deception inside chat, not broad infrastructure compromise. Upgrade planning should be prompt but can be risk-ranked against internet exposure and user base.
Technical view
CVE-2022-35251 is a persistent cross-site scripting issue in Rocket.Chat <v5 caused by style injection in the complete chat window. The CVSS 3.1 score is 5.4, requiring network access, low attack complexity, low privileges, and user interaction, with changed scope and low confidentiality and integrity impact.
Likely exposure
Exposure is most likely where Rocket.Chat is below v5 and allows authenticated or semi-trusted users to post messages viewed by staff, customers, or community members. Public or large shared workspaces carry higher practical risk because stored messages can affect later viewers.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. The vulnerability is persistent because payloads are stored in messages and trigger when viewed. Evidence supports targeted user impact, not server takeover or direct availability loss.
Researcher notes
Available evidence identifies CWE-79 and a stored style-injection vector in Rocket.Chat <v5. CVSS indicates privileges and user interaction are required. The bundle does not provide exploit prevalence, detailed patch notes, or broader affected product claims, so validation should stay version- and exposure-focused.
Mitigation direction
- Inventory Rocket.Chat deployments and identify any versions below v5.
- Upgrade affected Rocket.Chat instances to a vendor-supported fixed v5 or later release.
- Review Rocket.Chat vendor guidance before applying compensating controls.
- Restrict message posting in exposed workspaces until fixed.
- Preserve relevant logs before cleanup if suspicious messages are found.
Validation and detection
- Confirm each Rocket.Chat instance version against the fixed v5 threshold.
- Check whether public or untrusted users can post chat messages.
- Review message history for suspicious stored styling or content manipulation indicators.
- Verify upgraded instances render prior messages without triggering the reported behavior.
- Document affected workspaces, user populations, and remediation dates.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-35251 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N2.32.7Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.4MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://hackerone.com/reports/1401268CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.