OpenWA is a free, open source, self-hosted WhatsApp API gateway. Prior to 0.23.5, the /events WebSocket gateway delivers the session.qr event to a VIEWER API key that subscribes by event name or through either wildcard subscription form, even though GET /api/sessions/{sessionId}/qr requires the OPERATOR role. When an allowed session is waiting to be paired, the exposed QR lets the key holder link an external device to the WhatsApp account and then read and send messages outside OpenWA and its audit trail.
Keys restricted through allowedSessions remain limited to those sessions, and deployments that issue only OPERATOR or ADMIN keys are not affected. This issue is fixed in version 0.23.5.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
High
Difficult to exploit
Privileges Required
Low
Basic privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
High
Complete data leak
Integrity
High
Complete data modification
Availability
None
No disruption
CVSS Vector v3.1
Weakness Type (CWE)
References 5
https://github.com/rmyndharis/OpenWA/commit/acc23c3803c07f43791a92e8e48456572fd…
security-advisories@github.com
https://github.com/rmyndharis/OpenWA/commit/b9d9ea1c57bde98b7833a5d6e4829987036…
security-advisories@github.com
https://github.com/rmyndharis/OpenWA/pull/1602
security-advisories@github.com
https://github.com/rmyndharis/OpenWA/releases/tag/v0.23.5
security-advisories@github.com
https://github.com/rmyndharis/OpenWA/security/advisories/GHSA-m427-j4h4-9qwj
security-advisories@github.com