CVE-2026-53959
MediumCVSS 6.5Exploitation Probability (EPSS)
Low risk34th percentile - higher than 34% of all known CVEs
Summary
Vulnerability in 4gaBoards (before 3.3.9) allows any authenticated user to enumerate accounts and read data of all users via the /api/users API, without authorization.
Risk Assessment
Risk of privacy breach, exposure of personal data and email addresses, which can be used for phishing or further attacks.
Recommendation
Update 4gaBoards to version 3.3.9 or later, which includes the fix.
Other vulnerabilities in 4gaBoards
See all- CVE-2026-53958High
Vulnerability in 4gaBoards (before 3.3.9) allows an authenticated user to modify SSO identity attributes (e.g., ssoGoogleId) via PATCH /api/users/:id. An attacker can assign a victim's identifier to their account, leading to account takeover during the victim's first SSO login.
- CVE-2026-50191High
Vulnerability in 4gaBoards (before 3.3.8) allows pre-account takeover when registration and SSO are enabled. An attacker can create an unverified account with the victim's email, and during the victim's first SSO login, the SSO identity is linked to the attacker's account.
- CVE-2026-50186High
4gaBoards before version 3.3.8 allows an authenticated project manager to supply traversal sequences in the filename parameter of GET /exports/:id/:filename. In server/api/controllers/boards/download.js, the decoded inputs.filename value is passed to path.join() without containment validation, allowing arbitrary file read. The fileStream close handler then deletes the selected file, potentially causing data loss or DoS.
Original NVD description (English source)
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.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS