CVE-2026-50191
HighCVSS 8.8Exploitation Probability (EPSS)
Low risk26th percentile - higher than 26% of all known CVEs
Summary
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.
Risk Assessment
An attacker can gain access to the victim's account, projects, and data, posing a serious security risk.
Recommendation
Update 4gaBoards to version 3.3.8 or later. Require email verification before account activation.
Other vulnerabilities in 4gaBoards
See all- CVE-2026-53959Medium
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.
- 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-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.8, 4gaBoards is vulnerable to pre-account takeover when registrationEnabled, localRegistrationEnabled, and ssoRegistrationEnabled are enabled and Google, GitHub, Microsoft, or OIDC SSO is configured. The POST /api/register endpoint permits creation of an unverified local account with a victim's email address, and POST /api/access-tokens permits that account to authenticate while isVerified is false. During the victim's first SSO login, server/api/helpers/users/get-create-one-for-github-sso.js, server/api/helpers/users/get-create-one-for-google-sso.js, server/api/helpers/users/get-create-one-for-microsoft-sso.js, and server/api/helpers/users/get-create-one-for-oidc-sso.js find the attacker-controlled account by email and link the verified SSO identity without confirming ownership of the local account. The attacker can retain local-password access to the linked account and obtain the victim's projects, data, and permissions. This issue is fixed in version 3.3.8.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS