CVE-2026-53959: 4gaBoards: Mass Information Disclosure (Internal PII Leakage) on /api/users to any authenticated user

Published Aug 18, 2026
·
Updated

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.

Affected Software

1 affected component
4gaBoards<3.3.9

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade 4gaBoards to a version that resolves this vulnerability.

    Fixed in 3.3.9

Event History

Aug 18, 2026
CVE Published
via MITRE·09:35 PM
Data Sourced
via MITRE·09:35 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can exploit this issue?

Any authenticated 4gaBoards user can access the affected endpoints; administrator privileges are not required. The exposure includes information for all accounts, including administrators.

2

What does an attacker need to exploit it?

An attacker needs only a valid authenticated account and network access to the application. No user interaction or elevated permissions are required.

3

Are standard authenticated deployments affected?

The affected users/index and users/show actions rely solely on the default is-authenticated policy, so ordinary authenticated users are affected by the described authorization gap.

4

How can I investigate whether the issue has been abused?

Review access logs for GET requests to /api/users and /api/users/:id from non-administrative accounts, particularly requests that enumerate many user IDs. Upgrade to version 3.3.9 to address the issue.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203