Skip to content
Fencer Vulns
critical 9.8

CVE-2021-22911 in the critical feed json

A improper input sanitization vulnerability exists in Rocket.Chat server 3.11, 3.12 & 3.13 that could lead to unauthenticated NoSQL injecti…

published 2021-05-27 5 y ago modified 2026-06-17 4 mo ago also EUVD-2021-10040

cvss
9.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
95.2%
EPSS 95.2% chance of exploitation in 30 days, percentile 99.8%
public exploits
2
Exploit-DB, plus a Nuclei check

Summary

A improper input sanitization vulnerability exists in Rocket.Chat server 3.11, 3.12 & 3.13 that could lead to unauthenticated NoSQL injection, resulting potentially in RCE.

Timeline

  1. Published
  2. First public exploit (EDB-49960)

Exploit prediction

95.24% chance of exploitation in the next 30 days, higher than 99.8% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • EDB-50108 Rocket.Chat 3.12.1 - NoSQL Injection to RCE (Unauthenticated) (2) webapps, 2021-07-07
  • EDB-49960 Rocket.Chat 3.12.1 - NoSQL Injection (Unauthenticated) webapps, 2021-06-07
  • Nuclei template Rocket.Chat <=3.13 - NoSQL Injection nuclei detection template
  • hackerone.com https://hackerone.com/reports/1130721 referenced PoC, tagged "exploit" by a source, unverified
  • packetstormsecurity.com http://packetstormsecurity.com/files/162997/Rocket.Chat-3.12.1-NoSQL-Injection-Code-Execution.html referenced PoC, tagged "exploit" by a source, unverified
  • packetstormsecurity.com http://packetstormsecurity.com/files/163419/Rocket.Chat-3.12.1-NoSQL-Injection-Code-Execution.html referenced PoC, tagged "exploit" by a source, unverified
  • blog.sonarsource.com https://blog.sonarsource.com/nosql-injections-in-rocket-chat referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Affected products

  • n/a Rocket.Chat server

Classification

Weakness
  • CWE-75 Failure to Sanitize Special Elements into a Different Plane

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.