CVE-2022-32211: Rocket.Chat · SQL Injection
Affects Rocket.ChatSource CVE Database V5
Not known to be exploited · CVSS 8.8 High : upgrade to 3.18.6 soon.
Data as of 26 Oct 2026, 09:15 UTC
- EPSS
- 1.3% chance of exploitation in 30 days – higher than 71% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.18.6
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 23 Sep 2022
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade Rocket.Chat to 3.18.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| n/a Rocket.Chat | Affected
| Fixed in
|
AI-suggested
To mitigate CVE-2022-32211 effectively, European organizations should: 1) Immediately upgrade all Rocket.Chat instances to version 3.18.6, 4.4.4, 4.7.3, or later, where the vulnerability is patched. 2) Conduct a thorough audit of user accounts and authentication logs to detect any suspicious activity or unauthorized access attempts prior to patching. 3) Implement strict network segmentation and firewall rules to limit access to Rocket.Chat servers, restricting exposure to trusted internal networks or VPNs only. 4) Enforce the principle of least privilege by reviewing and minimizing user permissions within Rocket.Chat to reduce the impact of potential account compromise. 5) Enable and monitor multi-factor authentication (MFA) for all users to add an additional security layer beyond password resets. 6) Regularly back up Rocket.Chat data and configurations to enable recovery in case of compromise or data manipulation. 7) Monitor security advisories and threat intelligence feeds for any emerging exploit attempts targeting this vulnerability. 8) Consider deploying Web Application Firewalls (WAFs) with SQL injection detection and prevention capabilities to provide an additional defense layer against exploitation attempts.
Description
A SQL injection vulnerability exists in Rocket.Chat <v3.18.6, <v4.4.4 and <v4.7.3 which can allow an attacker to retrieve a reset password token through or a 2fa secret.