CVE-2026-53958
HighCVSS 7.6Exploitation Probability (EPSS)
Low risk28th percentile - higher than 28% of all known CVEs
Summary
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.
Risk Assessment
An attacker can take over a victim's account and gain access to their projects, data, and permissions, posing a serious security risk.
Recommendation
Update 4gaBoards to version 3.3.9 or later. Restrict users' ability to modify SSO attributes.
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-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 an authenticated user to modify ssoGoogleId, ssoGoogleEmail, ssoGithubId, ssoGithubUsername, ssoGithubEmail, ssoMicrosoftId, ssoMicrosoftEmail, ssoOidcId, and ssoOidcEmail through PATCH /api/users/:id. The whitelist in server/api/controllers/users/update.js mass assigns these backend-managed identity attributes from user input. An attacker can place a victim's provider identifier on an attacker-controlled account, causing the default lookup in helpers such as server/api/helpers/users/get-create-one-for-github-sso.js to match the victim's first SSO login to the attacker's account before the email-linkage flow runs. The victim is logged into the attacker-controlled account, and projects, boards, or data the victim creates remain accessible through the attacker's original local credentials. This issue is fixed in version 3.3.9.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS