4gaBoards: Mass Information Disclosure (Internal PII Leakage) on /api/users to any authenticated user
What fixes it
- 3.3.94gaboards, npmGitHub
npm install 4gaboards@3.3.9
A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.
Timeline
- 5 Jun 2026Exploit code publicMetasploit
- 18 Aug 2026, 21:35 UTCPublishedCVE List
Public exploit code and templates 1
- Auxiliary module4gaBoards Mass User Information Disclosure (CVE-2026-53959) 5 Jun 2026Metasploit
Listed so defenders can prioritize. Threatline links to the source and does not host exploit code.
Reports 1
1 outlet mention it. Reports are not confirmation; each links to its source.
Description
4gaBoards is a boards system for realtime project management. Prior to 3.3.9, 4gaBoards allows any authenticated user to enumerate account information for every user through GET /api/users and retrieve arbitrary accounts through GET /api/users/:id. The users/index and users/show actions rely only on the default is-authenticated policy in server/config/policies.js, and server/api/controllers/users/index.js returns the result of sails.helpers.users.getMany() without requester-specific authorization or response sanitization. Responses expose email, phone, organization, name, isAdmin, ssoGoogleEmail, ssoGithubEmail, and other SSO-linked email fields, including data for administrators. This enables instance-wide user enumeration, privacy loss, and targeted phishing reconnaissance. This issue is fixed in version 3.3.9.
Text from CVE List
Affected versions 2
- 4gaBoardsaffected: < 3.3.9CVE List
- 4gaboards, npm<= 3.3.8GitHub