CVE
Rocket.Chat unauthenticated message disclosure in livechat
Affects Rocket.Chat 0.61.0 up to 3.11.4, 3.12.0 up to 3.12.4, and 3.13.0 up to 3.13.2 through Live Chat. Fixed in 3.13.2.
- Exploited
- No known exploitation
- Fix
- Fixed in 3.11.4, 3.12.4, 3.13.2
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 3.11.4, 3.12.4, 3.13.2.
Summary
Rocket.Chat versions 0.61.0 before 3.11.4, 3.12.x before 3.12.4 and 3.13.x before 3.13.2 contain a missing authorization vulnerability allowing unauthenticated attackers to read any room's messages via the livechat:loadHistory Meteor method. Attackers can mint a guest token through livechat:registerGuest and send POST requests to /api/v1/method.callAnon with a target rid parameter to retrieve message history without membership checks. Exploitation evidence was first observed by the Shadowserver Foundation on 2025-02-13.
Who should check
Operators running Rocket.Chat 3.13.x builds older than 3.13.2, including servers with Live Chat enabled
“RocketChat Live Chat accepts invalid parameters”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 3.11.4, 3.12.4, 3.13.2.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2021-48022 (Rocket.Chat < 3.13.2 Unauthenticated IDOR via livechat:loadHistory), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2021-48022 (entry last updated 2026-11-18):
Affected:
- Rocket.Chat Rocket.Chat: from 0.61.0, fixed in 3.11.4; from 3.12.0, fixed in 3.12.4; from 3.13.0, fixed in 3.13.2
Fixed versions: 3.11.4, 3.12.4, 3.13.2.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2021-48022 is not listed as of cve.now's last read.
This KEV status is for CVE-2021-48022 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/RocketChat/Rocket.Chat/commit/9e63222893
- https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/rocketchat/unauth-message-read.yaml
- https://www.vulncheck.com/advisories/rocket-chat-before-3.13.2-unauthenticated-idor-via-livechat-loadhistory
- https://www.vulncheck.com/advisories/rocket-chat-3.13.2-unauthenticated-idor-via-livechat-loadhistory
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2021-48022
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2021-48022"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- Rocket.Chat Rocket.Chat
From 0.61.0 · fixed in 3.11.4; From 3.12.0 · fixed in 3.12.4; From 3.13.0 · fixed in 3.13.2
Evidence 7
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2021-48022 |
| Record | NVD · CVE-2021-48022 |
| Public exploit code 2Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub). | |
| Exploit | securifyinc.com · disclosures/rocketchat-unauthenticated-access-to-messages |
| Repository | GitHub · projectdiscovery/nuclei-templates · http/vulnerabilities/rocketchat/unauth-message-read.yaml |
| Other links 3 | |
| Patch | GitHub · RocketChat/Rocket.Chat · Commit 9e632228 |
| Link | vulncheck.com · advisories/rocket-chat-before-3.13.2-unauthenticated-idor-via-livechat-loadhistory |
| Link | vulncheck.com · advisories/rocket-chat-3.13.2-unauthenticated-idor-via-livechat-loadhistory |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2021-48022
Is CVE-2021-48022 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
Rocket.Chat Live Chat accepts invalid parameters that could allow unauthenticated access to chat messages and user tokens. The flaw is in the livechat:loadHistory handling.Source: github.com, github.com
Which versions are affected by CVE-2021-48022?
Rocket.Chat: from 0.61.0 before 3.11.4; from 3.12.0 before 3.12.4; from 3.13.0 before 3.13.2.Source: cve.now feed data
Am I affected, and how do I check?
Affected ranges are Rocket.Chat 0.61.0 up to 3.11.4, 3.12.0 up to 3.12.4, and 3.13.0 up to 3.13.2. Check the installed Rocket.Chat server version against these ranges.Source: github.com, github.com
How do I fix CVE-2021-48022?
Upgrade to Rocket.Chat 3.13.2, the fixed version listed for this vulnerability.Source: github.com, github.com