Severity by source
AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
Lifecycle Timeline
2DescriptionCVE.org
The /api/v1/autotranslate.translateMessage endpoint in versions <8.5.0, <8.4.2, <8.3.4, <8.2.4, <8.1.5, <8.0.6, <7.13.8, and <7.10.12 allows any authenticated user to retrieve the full content of any message from any room (private groups, direct messages, channels) by simply providing the target message ID. The endpoint fetches the message via Messages.findOneById(messageId) with no room access check (canAccessRoomIdAsync is never called), returning the complete IMessage object including message text, sender info, room ID, timestamps, and markdown content.
AnalysisAI
Broken access control on the /api/v1/autotranslate.translateMessage endpoint in Rocket.Chat allows any authenticated user to retrieve the full content of messages from rooms they have no membership in - including private groups, direct messages, and channels - by supplying only a valid message ID. The vulnerability stems from the complete absence of a room-level authorization check (canAccessRoomIdAsync is never invoked) before the message fetch via Messages.findOneById(). No public exploit code or CISA KEV listing has been identified at time of analysis, but the high confidentiality impact (C:H in CVSS) means successful exploitation exposes sensitive private communications organization-wide.
Technical ContextAI
The affected endpoint is a server-side REST API route in Rocket.Chat's autotranslate feature (CPE: cpe:2.3:a:rocket.chat:rocket.chat:*). When a translation request is submitted, the handler calls Messages.findOneById(messageId) to resolve the target message, but the standard room-access gate - canAccessRoomIdAsync - is never invoked. This is a textbook CWE-284 (Improper Access Control) instance: the application correctly authenticates the calling user but fails to enforce the authorization rule that restricts message visibility to room members. The returned IMessage object includes message text, sender identity, room ID, timestamps, and rendered markdown - the full data model - making this a complete confidentiality bypass rather than a partial information leak.
RemediationAI
Upgrade to the earliest fixed release in your respective version branch: 8.5.0, 8.4.2, 8.3.4, 8.2.4, 8.1.5, 8.0.6, 7.13.8, or 7.10.12. These version thresholds are derived directly from the CVE description's affected-version ranges; a patched release at each boundary is implied, but independent confirmation of fix-version release notes was not available in the provided data - verify against the Rocket.Chat changelog or HackerOne report at https://hackerone.com/reports/3713682. If immediate upgrade is not possible, a compensating control is to disable or restrict access to the /api/v1/autotranslate.translateMessage endpoint at the reverse-proxy or API gateway layer; note that this will break the autotranslate feature for all users. Additionally, auditing API access logs for calls to this endpoint from users outside of expected room memberships may help detect prior exploitation. Restricting user registration and revoking unused internal accounts reduces the PR:L attack surface while a patch is applied.
More in Rocket Chat
View allA sanitization vulnerability exists in Rocket.Chat server versions <3.13.2, <3.12.4, <3.11.4 that allowed queries to an
A improper input sanitization vulnerability exists in Rocket.Chat server 3.11, 3.12 & 3.13 that could lead to unauthenti
A improper authentication vulnerability exists in Rocket.Chat <v5, <v4.8.2 and <v4.7.5 that allowed two factor authentic
A SQL injection vulnerability exists in Rocket.Chat <v3.18.6, <v4.4.4 and <v4.7.3 which can allow an attacker to retriev
A Server-Side Request Forgery (SSRF) affects Rocket.Chat's Twilio webhook endpoint before version 6.10.1. Rated high sev
An information disclosure vulnerability exists in the Rocket.Chat server fixed v3.13, v3.12.2 & v3.11.3 that allowed ema
An improper authentication vulnerability exists in Rocket.Chat Mobile App <4.14.1.22788 that allowed an attacker with ph
A cleartext transmission of sensitive information exists in Rocket.Chat <v5, <v4.8.2 and <v4.7.5 relating to Oauth token
An information disclosure vulnerability exists in Rocket.Chat <v5 due to the getUserMentionsByChannel meteor server meth
Rocket.Chat is an open-source fully customizable communications platform developed in JavaScript. Rated medium severity
Rocket.Chat through 3.4.2 allows XSS where an attacker can send a specially crafted message to a channel or in a direct
Rocket.Chat before 2.1.0 allows XSS via a URL on a ![title] line. Rated medium severity (CVSS 6.1), this vulnerability i
Same weakness CWE-284 – Improper Access Control
View allSame technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-30835
GHSA-wm7g-8c9r-vg8p