CVE-2021-22911: A improper input sanitization vulnerability exists in Rocket.Chat server 3.11, 3.12 & 3.13 that could lead to unauthenticated NoSQL…
Noroxi assessment
Priority: This week (action score 68/100)
- A ready-made attack module is public (Nuclei); exploiting it takes no special expertise.
- Public proof-of-concept code exists (Exploit-DB, GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 95.2% (FIRST EPSS); higher than 99.8% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Don’t wait for the next maintenance window. Until a fix is released, restrict access to the affected component and follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- May 27, 2021
- Updated
- Jun 16, 2026
- EPSS
- 95.2% · 99th percentile
- CWE
- CWE-75
Report tools
Action score
68
Don’t wait for the next maintenance window.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 29 / 30 · 95.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| rocket.chat | rocket.chat | cpe:2.3:a:rocket.chat:rocket.chat |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- rocket.chat rocket.chat3.11.0
- rocket.chat rocket.chat3.12.0
- rocket.chat rocket.chat3.13.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (hackerone). Independent of NVD's CPE analysis and usually ahead of it.
n/a Rocket.Chat server
- Fixed in: 3.13.2, 3.12.4, 3.11.4affected
Same product
rocket.chat: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-44567A command injection vulnerability exists in Rocket.Chat-Desktop <3.8.14 that could allow an attacker to pass a malicious url of…40Plan
- CVE-2021-22910A sanitization vulnerability exists in Rocket.Chat server versions <3.13.2, <3.12.4, <3.11.4 that allowed queries to an endpoint which…40Plan
- CVE-2017-1000493Rocket.Chat Server version 0.59 and prior is vulnerable to a NoSQL injection leading to administrator account takeover40Plan
Published before and after this one in the same product
- ← EarlierCVE-2021-22886Mar 26, 2021 · Rocket.Chat before 3.11, 3.10.5, 3.9.7, 3.8.8 is vulnerable to persistent cross-site scripting (XSS) using nested markdown tags allowing a…25Monitor
- ← EarlierCVE-2021-22892May 27, 2021 · An information disclosure vulnerability exists in the Rocket.Chat server fixed v3.13, v3.12.2 & v3.11.3 that allowed email addresses to be…31Monitor
- Later →CVE-2020-26763Jul 5, 2021 · The Rocket.Chat desktop application 2.17.11 opens external links without user interaction.30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Exploit-DB entry ×2
- Nuclei detection template ×1
- Proof-of-concept repository on GitHub ×12
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Exploit-DB entry | webapps | 2021-06-07 |
| Exploit-DB entry | webapps | 2021-07-07 |
| Nuclei detection template | Nuclei template CVE-2021-22911 | — |
| Proof-of-concept repository on GitHub | stars:61 | 2021-06-05 |
| Proof-of-concept repository on GitHub | stars:10 | 2021-07-30 |
| Proof-of-concept repository on GitHub | stars:0 | 2021-09-19 |
| Proof-of-concept repository on GitHub | stars:0 | 2023-04-01 |
| Proof-of-concept repository on GitHub | stars:0 | 2023-06-05 |
| Proof-of-concept repository on GitHub | stars:0 | 2023-06-19 |
| Proof-of-concept repository on GitHub | stars:0 | 2024-12-26 |
| Proof-of-concept repository on GitHub | stars:0 | 2025-05-29 |
| Proof-of-concept repository on GitHub | stars:0 | 2026-02-25 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+9 d
- TodayNov 12, 2026+1995 d
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-75 · Failure to Sanitize Special Elements into a Different Plane (Special Element Injection)CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.