Executive brief
Rocket.Chat is a communications platform used for team collaboration and customer support. A security flaw in the visitor information system allows authorized staff members to access sensitive security tokens belonging to website visitors they are not supposed to manage. An attacker with staff-level access could use these leaked tokens to impersonate visitors, potentially accessing private chat histories or performing actions on their behalf.
Technical details
An improper authorization vulnerability (CWE-285) exists in the Rocket.Chat 'visitors.info' API endpoint. While the endpoint requires the 'view-l-room' permission, it fails to restrict access based on the caller's authorized room, department, or queue scope. By providing a specific 'visitorId', an authenticated attacker can retrieve a full visitor object that includes the visitor's bearer token, contact fields, and network metadata. This leaked token can be used to impersonate the visitor. The issue is resolved 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.
Affected products
- RocketChat Rocket.Chat < 7.10.12, 7.11.0-rc.0 to < 7.13.8, 8.0.0-rc.0 to < 8.0.6, 8.1.0-rc.0 to < 8.1.5, 8.2.0-rc.0 to < 8.2.4, 8.3.0-rc.0 to < 8.3.4, 8.4.0-rc.0 to < 8.4.2, 8.5.0-rc.0 to < 8.5.0
Timeline
- 2026-05-25: advisory: GitHub Security Advisory published by Rocket.Chat
- 2026-06-24: disclosed: CVE published to NVD