Severity by source
AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:L
Network-accessible API requires a low-privileged account (PR:L) and victim SSO login (UI:R); full read/write impact on victim data justifies C:H and I:H.
Primary rating from Vendor (github).
CVSS VectorVendor: github
Lifecycle Timeline
4DescriptionCVE.org
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.
AnalysisAI
SSO account takeover in 4gaBoards prior to version 3.3.9 allows any authenticated user to overwrite backend-managed OAuth identity fields on their own account via the PATCH /api/users/:id endpoint, redirecting a victim's SSO login to the attacker's account. The root cause is a mass-assignment flaw in server/api/controllers/users/update.js that incorrectly exposed SSO provider identifiers - including Google, GitHub, Microsoft, and OIDC subject IDs and emails - to user-controlled input. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | The attacker must hold a valid authenticated 4gaBoards account (PR:L confirmed by CVSS vector). … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 7.6 High score (AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:L) is well-calibrated for this vulnerability. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | Full exploit scenario with step-by-step reproduction available after sign-in. |
| Remediation | Upgrade to 4gaBoards version 3.3.9 or later immediately; this is the vendor-confirmed patched release available at https://github.com/RARgames/4gaBoards/releases/tag/v3.3.9. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, audit 4gaBoards access logs and account modification history to identify any unauthorized changes to user accounts, particularly those with elevated permissions, and coordinate with your SSO provider administrators (Google, GitHub, Microsoft, OIDC) to monitor for suspicious credential changes. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-287 – Improper Authentication
View allSame technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-62203